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]

Re: [ping] Re: [patch, powerpc] #undef LINK_EH_SPEC before defining it


On Fri, 4 Mar 2011, Alan Modra wrote:

> On Fri, Mar 04, 2011 at 08:38:18AM +0100, Jakub Jelinek wrote:
> > We see it because we add --no-add-needed to linux LINK_EH_SPECs.
> 
> OK.  Adding the #undef is then required..
> 
> > Including freebsd-spec.h in a Linux configuration is certainly very
> > questionable and undefining LINK_EH_SPEC and other macros before defining
> > them would be certainly cleaner if the freebsd-spec.h include can't be just
> > killed.
> 
> It's there for -mcall-freebsd.  Take that away and you won't need
> freebsd-spec.h in powerpc-linux configs.

I'd certainly like to see the -mcall-* code that pretends to support 
linking for one target using another target's compiler removed.  That way 
non-FreeBSD targets wouldn't need freebsd-spec.h, rs6000/sysv4.h wouldn't 
need loads of specs that are really irrelevant to all but one target, and 
you could probably make powerpc*-linux* use the toplevel gnu-user.h and 
linux.h like almost all other Linux kernel targets.  That these powerpc* 
targets are doing things differently from all other architectures is a 
nuisance when making changes across all targets (and I don't think what 
they are doing is a useful intermediate step towards a multi-target 
compiler).

-- 
Joseph S. Myers
joseph@codesourcery.com


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