Re: NetBSD/vax compiler bounty?

[Martin Husemann <martin%duskware.de@localhost>]

On Thu, Apr 16, 2020 at 09:22:52AM -0700, Jason Thorpe wrote:
> > Any idea, how long it actually takes, to compile gcc on a vax?
> 
> I don't think it's possible anymore due to memory consumption by the compiler.  That said, GCC doesn't self-host on a lot of targets (mainly the microcontroller ones), so I don't think this is a big deal.  We should focus on making a modern cross-vax-gcc work correctly.  As far as the test suite goes, perhaps a way to remotely execute the generated binaries (on a real machine or in a simulator) that need to run to ensure the compiler generated the correct code is the way to go... maybe the GCC test suite already supports that, even.

It mostly worked in gcc 4.8 times (and took a few days on my VAXStation 4000
Model 96 with 128 MB of ram and lots of swap space).

But Jason is right, self hosting is not the real issue we need to solve,
as long as it can compile things like bash, tcsh and a few other things
from pkgsrc.

My idea was to have a "natural" milestone for a seasoned gcc hacker to which
we could bind the full bounty.

Martin