This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: is -fno-toplevel-reorder going to deprecate
Hi, Ian
I mean exactly -fno-toplevel-reorder option. There are some compilers
which don't support it.
If option is going to deprecate in gcc in near future as well, than it
make sense to consider changes in glibc(eglibc).
So, there are no plans to deprecate option. Did I understand correctly?
Sergey Y.
2010/2/22 Ian Lance Taylor <iant@google.com>:
> Sergey Yakoushkin <sergey.yakoushkin@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.
>
> Ian