|Recommendable 68k C compilers harvard!rutgers!EDDIE.MIT.EDU!zrm (1987-08-19)|
|Re: Recommendable 68k C compilers decvax!ucbvax!hplabs!felix!preston (1987-08-20)|
|Re: Recommendable 68k C compilers zrm@EDDIE.MIT.EDU (1987-08-21)|
|Re: Recommendable 68k C compilers harvard!seismo!geac!daveb (1987-08-22)|
|Date:||Thu, 20 Aug 87 12:18:11 pdt|
|From:||decvax!ucbvax!hplabs!felix!preston (Preston Bannister)|
|Organization:||FileNet Corp., Costa Mesa, CA|
In article <672@ima.ISC.COM> you write:
>I need to find out what optimizing C compilers exist for the 68000. I
>have found, based on personal experience, that while Green Hills makes
>an awesome optimizing compiler, it gives up too much performance by
>using 32 bit ints, and it would be too painful to change the existing
>code I need to compile.
We use the Green Hills compiler here. I don't see how Green Hills
burns performance by using 32-bit ints. Especially since they seem to
benchmark faster than any other compiler! :-) In general it seems to
be a win, as the compiler places variables in registers whenever
possible, and the 68000's registers are 32-bit. My first take was that
16-bit int's might be more efficient, but there is some added overhead
for clearing out the upper part of the register.
Can you justify your statement?
Preston L. Bannister
USENET : ucbvax!trwrb!felix!preston
BIX : plb
CompuServe : 71350,3505
GEnie : p.bannister
Return to the
Search the comp.compilers archives again.