public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <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: Sun, 03 Apr 2011 11:21:00 -0000	[thread overview]
Message-ID: <bug-48418-4-lXTxS1Uuqw@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

--- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-04-03 11:21:27 UTC ---
It's deliberate that folding of references to const variables is now 
delayed - and ideally it would move out of the front end altogether.  
While decl_constant_value_for_optimization still exists it would be easy 
enough to have a second check for this warning in c_fully_fold_internal, 
but in general the alternatives (which are not mutually exclusive) are 
predictable warnings in the front end that may not catch all cases and may 
sometimes warn in unreachable code, and less-predictable middle-end 
warnings if the problem operation is reachable (here, if a shift by an 
out-of-range constant is found after optimization, which could include 
where the variable with the shift amount isn't marked const).


  parent reply	other threads:[~2011-04-03 11:21 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 [this message]
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
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-lXTxS1Uuqw@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).