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,a3ca574fc2007430 X-Google-Attributes: gid103376,public X-Google-Thread: 115aec,f41f1f25333fa601 X-Google-Attributes: gid115aec,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Ada and Automotive Industry Date: 1996/11/22 Message-ID: #1/1 X-Deja-AN: 198185462 references: <55ea3g$m1j@newsbf02.news.aol.com> <3280DA96.15FB@hso.link.com> <1996Nov6.210957.3070@ole.cdac.com> <5683sk$bsc@news.ccit.arizona.edu> organization: New York University newsgroups: comp.lang.ada,comp.realtime Date: 1996-11-22T00:00:00+00:00 List-Id: Ken Tindall says "I have seen what's been done for the 68HC11 with gcc: the implementation had to provide virtual 16- and 32-bit registers in RAM because gcc assumes a register rich architecture. The code quality is consequently poor. Of course, this is fine if all you want a free compiler to play with." Wonderful logic -- I have seen one attempt, it was poor, therefore it is impossible to do right. It is not true that gcc assumes a register rich architecture (after all it runs on the x86). Yes, I agree that targetting to an architecture like this will be more work, and that a half-baked job will be inefficient, but don't assume that means it is impossible.