public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/56470] [4.8 Regression] ICE output_operand: invalid shift operand
Date: Mon, 04 Mar 2013 07:01:00 -0000	[thread overview]
Message-ID: <bug-56470-4-7rmewSK0nP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56470-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56470

Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-03-04
     Ever Confirmed|0                           |1

--- Comment #1 from Richard Earnshaw <rearnsha at gcc dot gnu.org> 2013-03-04 07:01:07 UTC ---
Confirmed. 

I'm a bit wary of just truncating the value.  Shifts by 32 may be valid in the
ARM back-end in some circumstances where we're using the shift as part of
setting up the flags.

Fixing this fully would require getting rid of "shift_operator" and replacing
it with iterators.  But that's a pretty radical overhaul.  Long term that might
well be worthwhile, but not this close to a release.


  reply	other threads:[~2013-03-04  7:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27  9:40 [Bug target/56470] New: " jakub at gcc dot gnu.org
2013-03-04  7:01 ` rearnsha at gcc dot gnu.org [this message]
2013-03-04  8:18 ` [Bug target/56470] " jakub at gcc dot gnu.org
2013-03-05  7:02 ` rearnsha at gcc dot gnu.org
2013-03-05  9:15 ` jakub at gcc dot gnu.org
2013-03-06 10:27 ` rearnsha at gcc dot gnu.org
2013-03-08 15:46 ` [Bug target/56470] [4.7/4.8 " rguenth at gcc dot gnu.org
2013-03-11 11:49 ` rearnsha at gcc dot gnu.org
2013-03-11 14:38 ` [Bug target/56470] [4.7 " rearnsha at gcc dot gnu.org
2013-03-18 11:52 ` rearnsha at gcc dot gnu.org
2013-03-18 11:54 ` rearnsha 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-56470-4-7rmewSK0nP@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).