This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

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

Re: -ffunction-sections always on now?

To: Stan Shebs <shebs at apple dot com>
Subject: Re: -ffunction-sections always on now?
From: Jason Merrill <jason_merrill at redhat dot com>
Date: 02 Oct 2001 15:41:10 +0100
Cc: Benjamin Kosnik <bkoz at redhat dot com>, libstdc++ at gcc dot gnu dot org
References: <Pine.SOL.3.91.1011001191251.14324A-100000@taarna.cygnus.com><3BB925F0.A0CEC7D4@apple.com>

>>>>> "Stan" == Stan Shebs <shebs@apple.com> writes:

> Benjamin Kosnik wrote:
>> 
>> Hey stan, check out acinclude.m4
>> 
>> GLIBCPP_CHECK_COMPILER_FEATURES
>> 
>> If gcc can use these flags without barfing, they are turned on. If you
>> want to add a bit more intelligence to this, please do (but for ELF, it
>> should remain as is...)

> If I understand the test correctly, it's just testing that the
> compiler accepts the option, not that the resulting executable
> works.  That's possibly a bogosity in GCC, because I only turned
> on named sections to get Dwarf 2 sections of fixed names known
> to work with Mach-O, but that's taken to mean that the function
> section option works too, which doesn't really follow.

Sounds like we need another target macro.

Jason

References:
- Re: -ffunction-sections always on now?
  - From: Benjamin Kosnik
- Re: -ffunction-sections always on now?
  - From: Stan Shebs

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