This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 4.0.2/4.1 PATCH: Enforce PIC code for mips libffi (PR libgcj/21943)


On Fri, 10 Jun 2005, Richard Sandiford wrote:

> >> As so often with MIPS stuff, no-one would have really wanted the
> >> current situation.  Having GAS default to one thing and GCC default
> >> to the opposite is just plain silly.  The problem is, once you have
> >> that silliness, none of the possible ways of resolving it are
> >> "obviously" better than the others.
> >
> >  Agreed.  And I'm glad both default to the same settings consistently for 
> > Linux.
> > [...]
> >  Well, if you want to keep the IRIX setup strange, please feel free -- 
> > frankly I don't care at all.
> 
> Huh?  Like you said yourself in your earlier reply, mips*-linux-gnu GAS
> defaults to non-PIC too, just like IRIX does.  My point was that it's silly
> to have mips*-linux-gnu GAS default to one thing (when invoked directly)
> and mips*-linux-gnu GCC to default to the opposite.

 The underlying tool defaults to non-PIC, but if invoked through the GCC 
driver it does not.  As a result the behaviour of the setup is consistent 
for Linux -- for any language, including assembly, GCC produces PIC code 
by default and non-PIC if run with the "-mno-abicalls" option.  Your 
reason for doing it differently for IRIX is not immediately clear to me, 
but if you find it important, I won't argue.

 Of course normal users (i.e. non-toolchain developers) don't run gas 
directly, so the internals of the setup (no matter how silly) are not 
interesting to them -- it's the end result they care about.

  Maciej


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]