Port-vax archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Issues with compiler failures

On Sun, 17 Mar 2019 at 07:08, Martin Husemann <martin%duskware.de@localhost> wrote:
> On Sun, Mar 17, 2019 at 04:43:45AM +0000, maya%netbsd.org@localhost wrote:
> > Both are these failures are in reload specific code.
> > "Reload is the GCC equivalent of Satan." - GCC wiki
> > The best way moving forward would be to adapt the GCC VAX port to not
> > use reload.
> Or accept the fact that there is no active gcc maintainer upstream and
> everyone who has interest in VAX is not willing to spend enough time on
> gcc.
> An easier option would be to make pcc usable and accept it leads to some
> slightly reduced functionality (i.e. no groff, atf and libexecinfo in
> the base build due to missing c++ support).

pcc could also be a very good option for m68k and other platforms...

I know whomever works on this will be doing it for love not money, but
I'm happy to put $100 towards beverage money for anyone who gets
NetBSD VAX either building with pcc or hacks VAX gcc to not use reload


Home | Main Index | Thread Index | Old Index