On Mon, Feb 22, 2010 at 9:21 PM, Ian Lance Taylor <i...@google.com> wrote:
> Sergey Yakoushkin <sergey.yakoush...@gmail.com> writes:
>
>> I'm cross-compiling glibc(eglibc) for new processor.
>> As far as I can see -fno-toplevel-reorder option is critical for
>> successful build.
>> Without option some files (initfini.c, source for crt*.o) can be miscompiled.
>>
>> I've heard that option might become deprecated in future gcc versions
>> (e.g. 4.6).
>> Although, I don't have any evidence. Could you please clarify?
>
> Where did you hear that?
>
> I have not heard of any plans to deprecate -fno-toplevel-reorder.  As
> you say, it is required for certains kinds of use.  The gcc build even
> uses it itself.
>
> It's possible that you have this confused with -fno-unit-at-a-time.
> That option is deprecated.  It is being replaced with
> -fno-toplevel-reorder and -fno-section-anchors.

-fno-toplevel-reorder is something that will likely not work with
link-time optimization for example.  Though we could simply
mark units compiled with -fno-toplevel-reorder ineligible for LTO.

Richard.

> Ian
>

Reply via email to