On Fri, Mar 04, 2011 at 03:50:48PM +, Joseph S. Myers wrote:
> 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 l
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
> >
On Fri, Mar 04, 2011 at 10:13:02PM +1030, Alan Modra wrote:
> > 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
> > kille
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 ma
On Fri, Mar 04, 2011 at 05:30:10PM +1030, Alan Modra wrote:
> On Wed, Feb 16, 2011 at 11:36:09PM +0100, Matthias Klose wrote:
> > >../../src/gcc/config/rs6000/sysv4.h:839:1: warning: "LINK_EH_SPEC"
> > >redefined
> > >In file included from ./tm.h:33,
> > >from ../../src/gcc/cp/rtti.c:27:
> > >../.
On Wed, Feb 16, 2011 at 11:36:09PM +0100, Matthias Klose wrote:
> >../../src/gcc/config/rs6000/sysv4.h:839:1: warning: "LINK_EH_SPEC" redefined
> >In file included from ./tm.h:33,
> >from ../../src/gcc/cp/rtti.c:27:
> >../../src/gcc/config/freebsd-spec.h:135:1: warning: this is the location of
> >
