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,c30642befcd7bf85 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: New GNAT ports (was Re: Ada and Automotive Industry) Date: 1997/01/11 Message-ID: #1/1 X-Deja-AN: 209147752 references: <5asvku$jtu$1@goanna.cs.rmit.edu.au> <32D39F37.7F1F@mailgw.sanders.lockheed.com> <5b252e$fk4$1@goanna.cs.rmit.edu.au> organization: New York University newsgroups: comp.lang.ada Date: 1997-01-11T00:00:00+00:00 List-Id: Robert Eachus says " For the 8051, starting with an the a version of gcc for the Intel 8086, 80186, 80286, or even the Z-80 should be a good start. But a gcc version that targets are 386 or higher is probably a waste of effort as a starting point." This is a little confused. There is only one version of GCC, which is common across all targets. What specializes GCC to a particular target is the machine description file, which is essentially a formal description of the semantics of the target architecture. I don't see that the MD file for the 8086 would be a particularly helpful starting point for the 8051, except perhaps as a general indication of how MD files are written, although if you are not already thoroughly familiar with the mechanics of writing MD files for GCC, then you would be unlikely to succeed anyway with the 8051, which as has often been discussed here, is not an easy machine to target. Now it is also the case that if you tried to do an efficient GCC port to the 8051, you might well need to make some improvements in GCC, that's a steady process, and often driven by requirements that are initially generated by targetting to new architectures. The general idea here is not to put in special kludges for particular architectures (there is almost no specialization of this kind in GCC), but rather to abstract the general features involved, and provide enhancements that will be useful to any targets sharing the particular features involved. So it is quite likely that the 8051 might suggest some general improvements of this type, but there again, I doubt the 8086 would be a useful comparison point.