Re: PA specifies invalid T_ADAFLAGS

[law@redhat.com]

In message <200204252014.g3PKEb5K022548@hiauly1.hia.nrc.ca>, "John David Anglin
" writes:
 > > I'm not terribly familiar with gcc's configure / build system, so I don't
 > > know who's at fault here.  Should PA be specifying this in X_ADAFLAGS?
 > > Should Ada not be using T_ADAFLAGS like this?
 > 
 > I believe that this suggestion is correct.  We should be specifying
 > X_ADAFLAGS in a "x-" file, or files.  It's the host not the
 > target that's affected by this issue.  The appropriate xmake_file
 > defines need to be added to config.gcc.  I think we only want to do
 > this for the hpux, bsd and osf configurations (ie., those that use
 > the SOM linker and hppa64).  The pro doesn't use space registers.
 > Linux puts the same value in all the relevant space registers.
 > Don't know about the memory models for the other elf ports.
Actually OSF puts the same value in all the space registers.  I don't
recall what BSD did.  Not that it matters, I don't believe anyone is
still running the UofU BSD or OSF1 ports.

The few embedded PAs were level 0 implementations -- which don't have
space registers at all.

jeff