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: kenner@lab.ultra.nyu.edu (Richard Kenner) Subject: Re: GNAT & GCC performace (bad news) Date: 1999/12/17 Message-ID: #1/1 X-Deja-AN: 561882616 References: <82hn65$a5o$1@nnrp1.deja.com> <384FEBF9.5F4F6BD2@ftw.rsc.raytheon.com> X-Trace: typhoon.nyu.edu 945423325 128.122.140.194 (Fri, 17 Dec 1999 04:35:25 EDT) Organization: New York University Ultracomputer Research Lab NNTP-Posting-Date: Fri, 17 Dec 1999 04:35:25 EDT Newsgroups: comp.lang.ada Date: 1999-12-17T00:00:00+00:00 List-Id: In article <384FEBF9.5F4F6BD2@ftw.rsc.raytheon.com> Wes Groleau writes: >> The trouble is that a lot of information is lost in going from >> Ada to C. In particular, the typing information, which is >> extremely valuable for many kinds of optimization (e.g. alias >> analysis) is simply lost in the translation to C. > >But how much (if any) of this information is also lost by going from Ada >to the common intermediate format used by the GCC suite? That's hard to answer in detail since the information that's "lost" is what the backend currently can't use. But the major point is that this is not a fixed thing: the intermediate format keeps growing as the backend can make use of more data, so there is room for continual improvement in this area, while in converting to C, there's very limited room for passing on more such information to the C compiler.