[Coco] [Color Computer] C compiler for 6809

[Joel Ewy]

Gene Heskett wrote:
> On Saturday 05 May 2007, Manney wrote:
>   
>> Willard Goosey wrote:
>>     
>>>> From: "twand76" <twand76 at yahoo.com.au>
>>>> Date: Sat, 05 May 2007 05:41:21 -0000
>>>>
>>>> Can anyone recommend a good cheap (free) c compiler for the COCO3?
>>>>         
>>> There's also a port of Small C (for OS-9) on rtsi.  I've never used
>>> it, so I can't really say if it qualifies as "good" or not.
>>>
>>> There was a native DECB C compiler, or at least someone did an ad for
>>> it in Rainbow back in the day, but I don't know of anyone who has a
>>> copy.
>>>
>>> Otherwise, you're looking at cross-compiling, and I'm not sure what
>>> the status of the GCC port is.  Anyone?
>>>
>>> Willard
>>>       
>> I thought the gcc6809 project was dead?
>>     
>
> I don't think so Manny, see <http://www.oddchange.com/gcc6809/> for its 
> current status.  From that page, to download, you'll need a working SVN 
> client.  Apparently its working pretty well with gcc-3.4.6, but not as well 
> with the gcc-4.1.  From that web page, its a one man project unless someone 
> with compiler writing knowledge were to offer to help.  Its been over a 
> decade since I last fooled with c.prep.  I don't think that would make 
> me "qualified" to muck around in the internals. :)
>
>   
This is kind of interesting, as the current discussion on the (dare I
mention a Linux distro by name?) Debian-M68k mail list is about patches
to make GCC 4.1 and 4.2 produce proper code for the 68K architecture.  A
buggy GCC 4.1 was what slowed the building of packages down to the point
that M68k got dropped from the official release of Etch and has to
appear alongside Etch as an unofficial co-release.

Wouldn't the Debian-M68k guys be amused to learn that 4.1 doesn't work
on the 6809 either?

:)
JCE
> I have little actual knowledge, but would assume that gcc-3.4-compat (or 
> similarly named packages) would have to be installed on a linux box, as all 
> recent distros are now shipping a gcc-4.1 variant, which makes better code, 
> but is also a bit slower.
>
> We have a linux utility called ccache that can speed that up, it caches 
> compiler output modules, and if the checksum of the individual src file has 
> not changed, then on subsequent passes to rebuild the same module, it 
> intercepts the compiler calls and pulls the object back out of the cache.  
> For building kernels, that can cut a 20+ minute compile time down to 3 or 4, 
> which is rather handy.
>
> If running gcc6809 is slow, you might consider installing ccache too.  But its 
> little or no help when building something new that it has not seen before.
>
>   
>> -M.
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>     
>
>
>
>