[Coco] Retrochallenge -- Micro-C for CoCo

[billg999 at cs.uofs.edu]

> On 2013-07-31 10:57, Luis Antoniosi (CoCoDemus) wrote:
>> I think John wants a compiler for DECB.
>>
>> I have tried the gcc6809 and it made a code for DECB and seemed to run
>> fine. But gcc is meant for multiple registers processors so the speed
>> would
>> never be optimal.
>
> gcc6809 actually does a remarkable job when optimization for size is
> enabled. It could probably do a much better job with some tweaking but
> that's a harder job than it looks like (I've tried). The biggest problem
> with the most recent "official" version of gcc6809 is that it does not
> build properly on a 64 bit linux platform - it has issues related to
> word size - and porting it forward to a newer version of gcc is not
> pleasant due to some massive changes to the gcc internals.

Yeah, in moving our department servers forward to 64bit processors
I watched a lot of the ports build and I am amazed at how many
warnings are issued.  Rather than trying to add new features it's
time for the Open Source World to go back and just fix the stuff
they have out there now.  Is it really so hard to fix something in
the first place rather than leave it until it moves from a warning
to a bug?  Things like casting to/from pointers to items of different
sizes. Using un-initialized variables. Passing incompatible parameters
to functions.  Really......


bill