From: Samuel Bronson <naesten@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: gl_MANYWARN_ALL_GCC() leads to many spurious warnings
Date: Tue, 10 Jul 2012 14:07:10 -0400 [thread overview]
Message-ID: <C42138E7-7AA8-489A-86A3-76FC6B301F26@gmail.com> (raw)
In-Reply-To: <F3F156F3-D2CD-45EE-8459-D01D7823D0F7@gmail.com>
On Jul 9, 2012, at 11:23 AM, Samuel Bronson wrote:
> On Jul 8, 2012, at 10:15 PM, Paul Eggert wrote:
>
>> On 07/08/2012 07:10 AM, Samuel Bronson wrote:
>>
>>> I don't really know how to go about investigating that, short of
>>> building GCC manually
>>
>> I wasn't thinking of anything that drastic -- just
>> compile with gcc -E instead of gcc -c and look
>> to see what happened to the pragmas, something like that.
>>
>> I just now tried with stock Ubuntu 12.04, i.e.,
>> gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3, with
>> its bundled GNUstep libraries, and did not observe
>> either the regex.c -Wunused-macros warnings or the
>> -Wformat-security warnings. So this is not merely
>> a GCC 4.7.1 issue, for whatever that's worth. I
>> did see a passle of other warnings. Perhaps the
>> warnings that you're observing come up only after
>> you fix the ones I saw?
>
> Hmm. I'm beginning to suspect that the regex.c warnings are somehow
> related to my use of ccache...
Well, I was right; it was related to my use of ccache. But it's still
a GCC bug; gcc -E isn't honoring #pragma diagnostic ignored "-Wunused-
macros", and since ccache defaults to running the preprocessor first,
then compiling its output (so it can skip the compilation if it
already has results cached for that preprocessor output), this causes
ccache to output the bogus warnings. I reported this as <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53920
>.
Presumably, the reason that you don't get the format warnings with
GNUstep because, since only Apple's compilers have full support for
__attribute__((format(NSString,...)), GNUstep probably doesn't use
this attribute in its prototype for NSLog. I submitted a bug report
about them at <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53905>.
prev parent reply other threads:[~2012-07-10 18:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 21:17 gl_MANYWARN_ALL_GCC() leads to many spurious warnings Samuel Bronson
2012-07-06 21:41 ` Paul Eggert
2012-07-06 22:38 ` Samuel Bronson
2012-07-07 19:53 ` Paul Eggert
2012-07-08 0:41 ` Samuel Bronson
2012-07-08 7:32 ` Paul Eggert
2012-07-08 14:10 ` Samuel Bronson
2012-07-09 2:15 ` Paul Eggert
2012-07-09 15:23 ` Samuel Bronson
2012-07-10 18:07 ` Samuel Bronson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C42138E7-7AA8-489A-86A3-76FC6B301F26@gmail.com \
--to=naesten@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.