This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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] |
On Thu, 2009-05-07 at 14:17 +0200, Laurent GUERBY wrote: > On Thu, 2009-05-07 at 14:10 +0200, Arnaud Charlet wrote: > > Actually that's not what we want: what we want is to have --GCC be > > smarter and recognize that the compiler specified is "gcc" or "another > > non GCC compiler", which would also solve this issue. > > Ok if this was the idea behind the --GCC behaviour I believe it's easy > to extend the current gnatlink --GCC check to accept "xgcc" as well > as what it accepts now: > > gcc/ada/gnatlink.adb: > > if Program_Args.all (1).all /= Gcc.all then > Gcc := new String'(Program_Args.all (1).all); > Standard_Gcc := False; > end if; > > I will submit a new patch shortly, thanks for your help on this issue. Here it is. I've not changed the documentation because in the light about what you said about the intended semantics I think it covers xgcc as well since it's gcc too :). If ok I'll test it on mipsel before commiting. Also is it okay to backport on 4.4 as well? Laurent 2009-05-07 Laurent GUERBY <laurent@guerby.net> * gnatlink.adb: In the --GCC= case recognize xgcc in addition to gcc. * lib/gnat.exp: Fix whitespace. Use --GCC= for gnatlink.
Attachment:
patch-gnatlink-v4.txt
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |