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: 115aec,f41f1f25333fa601 X-Google-Attributes: gid115aec,public X-Google-Thread: 103376,a3ca574fc2007430 X-Google-Attributes: gid103376,public From: kenner@lab.ultra.nyu.edu (Richard Kenner) Subject: Re: Ada and Automotive Industry Date: 1996/11/22 Message-ID: <5743un$muj@news.nyu.edu>#1/1 X-Deja-AN: 198248931 distribution: world references: organization: New York University Ultracomputer Research Lab newsgroups: comp.lang.ada,comp.realtime Date: 1996-11-22T00:00:00+00:00 List-Id: In article ken@nrtt.demon.co.uk writes: >I have seen what's been done for the 68HC11 with gcc: There is no GCC port to the 68HC11 and none has ever been submitted for consideration in the years I've been in charge of GCC maintenance. What you must be talking about is somebody's preliminary attempt to port GCC to that processor. Clearly they didn't even think enough of it to submit it for consideration in the GCC release. So it is not reasonable to use it as a judge for what a proper port might look at. >gcc assumes a register rich architecture. GCC makes no such assumption. It knows precisely how many registers are available and what each can do. It does tend to do better on machines that have a lot of registers, but that's true for most compilers. >The code quality is consequently poor. The code quality is poor most likely because the person who did the port did it badly. It is somewhat tricky to do a port to a machine with a small number of registers because some of the config file macros that select which hueristics to use are relatively unimportant on machines with lots of registers, but are much more important on machines with only a few.