From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,4b12a5cee4778f63
X-Google-Attributes: gid103376,public
From: nabbasi@pacbell.net
Subject: Re: GNAT & GCC performace (bad news)
Date: 1999/12/02
Message-ID: <826rts$2fd1@drn.newsguy.com>#1/1
X-Deja-AN: 555979568
References: <B46CA6A1.2991%Harald.Schmidt@tomcat.de>
Organization: -
Newsgroups: comp.lang.ada
Date: 1999-12-02T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <B46CA6A1.2991%Harald.Schmidt@tomcat.de>, Harald says...
 
>What I was expecting,
>because gnat isn't a compiler env. but a to-C(++) translator,
>the performance decrease about ten to twenty percent but
>not 50 percent.
>
 
Gnat is not a "to-c" translator. Gnat is a front end, it does the
lexical and semantic analysis of the ada source code, and generates
the same input to the backend that other gnu languages generate, which
the backend uses to emit assembler code. (I assume some sort on internal
tree data representation in some common format that all front end gnu
compiler generate).


               +----+
  gnat ------> |    |      common
  gcc  ------> |    | ---> backend -----> assembler
  g++  ------> |    |
  f77  ------> |    |
               +----+
        front   intermidate
        end     data rep.

   
Nasser