[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: manywarnings and -f options

From: Eric Blake
Subject: Re: manywarnings and -f options
Date: Sat, 03 Dec 2011 11:21:37 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0

On 12/03/2011 09:00 AM, Simon Josefsson wrote:
> What does -funit-at-a-time really do?  My gcc 4.4 manual says:
> `-funit-at-a-time'
>      This option is left for compatibility reasons. `-funit-at-a-time'
>      has no effect, while `-fno-unit-at-a-time' implies
>      `-fno-toplevel-reorder' and `-fno-section-anchors'.
>      Enabled by default.

That's the case for 4.4 and later.  But in gcc 4.3, it was not
unconditionally enabled, and as I said earlier, at least coreutils ran
into a situation where gcc 4.3. failed to compile at -Werror because
-Wdisabled-optimization warned that -fno-unit-at-a-time was required,
which warning turned into an error.

At this point, gcc 4.3 is slowly phasing out; most Linux distros and
Cygwin have moved on to newer compilers, where the problem is less
likely to happen.

> The manual for -ipa-pure-const says:
> `-fipa-pure-const'
>      Discover which functions are pure or constant.  Enabled by default
>      at `-O' and higher.
> That seems harmless and as far I understand would not modify code
> generation.

It doesn't modify code generation, but it DOES modify warning
generation, and in a way that negatively interacts with libtool:

Eric Blake   address@hidden    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]