the Right place to change a target default for a common compiler flag?

2009-09-23 Thread IainS
Hi, In the case that a compiler flag in common.opt would best be served with different default values on different targets. I.E. a target-dependent Init() Where can this be effected in the machinery ? I can see how to make an override - but not a default. cheers, Iain

Re: the Right place to change a target default for a common compiler flag?

2009-09-23 Thread Joern Rennecke
Quoting IainS develo...@sandoe-acoustics.co.uk: Hi, In the case that a compiler flag in common.opt would best be served with different default values on different targets. I.E. a target-dependent Init() Where can this be effected in the machinery ? I can see how to make an override - but

Re: the Right place to change a target default for a common compiler flag?

2009-09-23 Thread Dominique Dhumieres
Iain, I am currently bootstrapping on i686-apple-darwin9 with the current patch: diff -uN /opt/gcc/_gcc_clean/config/mh-intel-darwin /opt/gcc/gcc-4.5-work/config/mh-intel-darwin --- /opt/gcc/_gcc_clean/config/mh-intel-darwin 1970-01-01 01:00:00.0 +0100 +++

Re: the Right place to change a target default for a common compiler flag?

2009-09-23 Thread IainS
Hi Dominique, I would expect you to need -gstrict-dwarf in CFLAGS_FOR_TARGET also but the point of my question is to find a way of having this on by default on Darwin (which is what we currently seem to need). (more research is need on the latter - to determine whether the problem lies

Re: the Right place to change a target default for a common compiler flag?

2009-09-23 Thread Dominique Dhumieres
With the previous patch, bootstrap failed when building libgomp: -gstrict-dwarf was not passed during the configure stage. So it is not sufficient to pass it to BOOT_CFLAGS. Would repeating the trick for CFLAGS_FOR_TARGET have a chance to work? Dominique