Re: Issues with compiler failures

[Paul Koning <paulkoning%comcast.net@localhost>]

> On Mar 17, 2019, at 9:44 AM, maya%netbsd.org@localhost wrote:
> 
> On Sun, Mar 17, 2019 at 09:33:44AM -0400, Paul Koning wrote:
>> 
>> 
>>> On Mar 17, 2019, at 3:07 AM, 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.
>> 
>> Is there no one willing to take on the gcc maintainer role for vax?  It's not rocket science.
>> 
>> 	paul
>> 
>> 
> 
> Will you be able to mentor? :-)

To a small extent, but I'm no GCC wizard.  I know it well enough to keep the pdp11 port alive, which is as GCC projects goes a modest challenge.  (Then again, the vax port is in the same ballpark, actually easier in some ways for example because it only has one condition code register rather than two.)

The gcc developers list is quite helpful, and unlike some other GNU projects GCC actually has an internals manual that is of high quality -- especially the part that deals with ports.

	paul