public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/48418] [4.5/4.6/4.7 Regression] Bit shift operator >>=
Date: Wed, 24 Aug 2011 20:52:00 -0000 [thread overview]
Message-ID: <bug-48418-4-wpwHAthdsh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48418-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48418
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P2 |P3
CC| |rguenth at gcc dot gnu.org
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-08-24 20:47:06 UTC ---
Richard, can you explain why this is a P2? the warning is only a regression in
the sense we would warn about about one case but not any more and the code is
undefined at runtime which means we should warn about it in all cases but
currently don't.
next prev parent reply other threads:[~2011-08-24 20:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 20:30 [Bug c/48418] New: " lisp2d at lisp2d dot net
2011-04-02 21:07 ` [Bug c/48418] " ebotcazou at gcc dot gnu.org
2011-04-02 21:43 ` d.g.gorbachev at gmail dot com
2011-04-03 11:09 ` [Bug c/48418] [4.5/4.6/4.7 Regression] " rguenth at gcc dot gnu.org
2011-04-03 11:21 ` joseph at codesourcery dot com
2011-04-10 10:47 ` rguenth at gcc dot gnu.org
2011-04-28 15:23 ` rguenth at gcc dot gnu.org
2011-08-24 20:52 ` pinskia at gcc dot gnu.org [this message]
2011-08-25 7:19 ` rguenth at gcc dot gnu.org
2012-07-02 11:25 ` [Bug c/48418] [4.5/4.6/4.7/4.8 " rguenth at gcc dot gnu.org
2013-01-08 14:45 ` [Bug c/48418] [4.6/4.7/4.8 " jakub at gcc dot gnu.org
2013-01-09 14:51 ` jakub at gcc dot gnu.org
2013-01-09 15:03 ` [Bug c/48418] [4.6/4.7 " jakub at gcc dot gnu.org
2013-02-01 9:11 ` jakub at gcc dot gnu.org
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=bug-48418-4-wpwHAthdsh@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).