From: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
To: Richard Henderson <rth@redhat.com>
Cc: DJ Delorie <dj@redhat.com>,
mark@codesourcery.com, joseph@codesourcery.com,
gcc-patches@gcc.gnu.org
Subject: Re: patch: honor volatile bitfield types
Date: Tue, 15 Jun 2010 19:27:00 -0000 [thread overview]
Message-ID: <AANLkTilwzHPNswKPF2Db7-BtFuzVoF6jlSLENZ4X2423@mail.gmail.com> (raw)
In-Reply-To: <4C17D051.2050405@redhat.com>
On 15 June 2010 21:11, Richard Henderson <rth@redhat.com> wrote:
> On 06/15/2010 09:54 AM, DJ Delorie wrote:
>>> Is this second message more approriate to "info" than "warning"?
>>
>> Yes, but I wanted to keep them in sync wrt enabling/disabling
>> diagnostics by type.
>
> You mean e.g. "-w" disabling warnings? I suppose that does
> require a bit of extra logic. Though that would be easier
> if warning returned a value indicating if the warning was
> actually emitted...
/* A warning at LOCATION. Use this for code which is correct according to the
relevant language specification but is likely to be buggy anyway.
Returns true if the warning was printed, false if it was inhibited. */
bool
warning_at (location_t location, int opt, const char *gmsgid, ...)
The same goes for pedwarn and permerror. This has been implemented
years ago for precisely this case.
Cheers,
Manuel.
prev parent reply other threads:[~2010-06-15 19:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 4:42 DJ Delorie
2010-06-11 9:55 ` Joseph S. Myers
2010-06-11 14:42 ` DJ Delorie
2010-06-11 16:42 ` Mark Mitchell
2010-06-11 16:56 ` Jeff Law
2010-06-11 23:23 ` DJ Delorie
2010-06-12 2:28 ` Mark Mitchell
2010-06-12 3:45 ` DJ Delorie
2010-06-12 4:12 ` Mark Mitchell
2010-06-12 10:17 ` Richard Guenther
2010-06-15 2:40 ` DJ Delorie
2010-06-15 3:01 ` Mark Mitchell
2010-06-15 5:16 ` DJ Delorie
2010-06-15 6:00 ` Mark Mitchell
2010-06-15 22:29 ` DJ Delorie
2010-06-15 22:45 ` Manuel López-Ibáñez
2010-06-15 22:55 ` DJ Delorie
2010-06-15 23:02 ` Mark Mitchell
2010-06-17 7:58 ` DJ Delorie
2010-06-22 10:42 ` Eric Botcazou
2010-06-22 18:32 ` DJ Delorie
2010-06-22 18:39 ` Eric Botcazou
2010-06-22 18:57 ` DJ Delorie
2010-06-22 20:04 ` Eric Botcazou
2010-06-23 0:51 ` DJ Delorie
2010-09-03 18:41 ` Jie Zhang
2010-06-15 23:03 ` Manuel López-Ibáñez
2010-06-16 0:43 ` DJ Delorie
2010-06-16 4:23 ` Mark Mitchell
2010-06-15 22:55 ` DJ Delorie
2010-06-15 8:32 ` Manuel López-Ibáñez
2010-06-15 17:53 ` Richard Henderson
2010-06-15 17:26 ` DJ Delorie
2010-06-15 17:35 ` Manuel López-Ibáñez
2010-06-15 19:20 ` Richard Henderson
2010-06-15 19:27 ` Manuel López-Ibáñez [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=AANLkTilwzHPNswKPF2Db7-BtFuzVoF6jlSLENZ4X2423@mail.gmail.com \
--to=lopezibanez@gmail.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=mark@codesourcery.com \
--cc=rth@redhat.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).