This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [patch] avoid ABI warnings on arm when running the libstdc++v3 testsuite
- From: Paolo Carlini <paolo dot carlini at oracle dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: Matthias Klose <doko at ubuntu dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>, "libstdc++ at gcc dot gnu dot org" <libstdc++ at gcc dot gnu dot org>, Mark Mitchell <mark at codesourcery dot com>
- Date: Fri, 15 Jan 2010 01:36:33 +0100
- Subject: Re: [patch] avoid ABI warnings on arm when running the libstdc++v3 testsuite
- References: <4B4F5A66.6020009@ubuntu.com> <4B4F5C6A.9050808@oracle.com> <Pine.LNX.4.64.1001150010530.20443@digraph.polyomino.org.uk>
On 01/15/2010 01:22 AM, Joseph S. Myers wrote:
> On Thu, 14 Jan 2010, Paolo Carlini wrote:
>
>
>> On 01/14/2010 06:54 PM, Matthias Klose wrote:
>>
>>> The attached patch runs the testsuite with -Wno-abi on arm targets. Ok
>>> for the trunk and the 4.4 branch? Should the target be more restricted?
>>>
>> Does not seem the right fix to me, the real issue is that *user code*
>> will warn, unless the user passes -Wno-abi! How happens that a system
>> header spills a warning, again? We have been working on those issues for
>>
> (a) It's a note (inform ()), not a warning; the general system header
> warning suppression may not work for those.
>
Interesting clarification... Now, why such inform are enabled and
disabled via -W options? And why the manuale describes -Wabi as: "Warn
when G++ generates..."? Frankly I'm quite a bit confused...
Anyway, besides these "theoretical" and academic curiosities of mine, I
hope we all agree that any diagnostic message != hard error, in other
terms, anything allowing anyway compilation to proceed, should be
suppressed in system headers. Pragmatically, I don't think we really
care about anything else, especially at this Stage.
Paolo.