From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org, fortran@gcc.gnu.org
Subject: Re: PATCH RFA: -Wc++-compat warnings for assignments to enum variables
Date: Wed, 22 Apr 2009 22:10:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0904222143290.20307@digraph.polyomino.org.uk> (raw)
In-Reply-To: <m3ab6875tm.fsf@google.com>
On Wed, 22 Apr 2009, Ian Lance Taylor wrote:
> There are two patches here. The first, smaller, patch enables the
> warning. The main work here is to add a parameter to build_modify_expr,
> so that we can emit warnings for assignments to bitfields in structs
> with enum type. The additional parameter is required because at the
> point of convert_for_assignment, the original enum type has been
> replaced by a bitfield integer type. This patch requires approval from
> the C and C++ frontend maintainers. Please also take a quick look at
> the new test case, and let me know if there are any other cases I should
> check.
The C changes are OK.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2009-04-22 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 21:11 Ian Lance Taylor
2009-04-22 22:10 ` Joseph S. Myers [this message]
2009-04-22 22:54 ` Tom Tromey
2009-04-23 20:03 ` Janne Blomqvist
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=Pine.LNX.4.64.0904222143290.20307@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=java-patches@gcc.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.
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).