public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "belagod at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/61114] Scalar evolution hides a big-endian const-folding bug.
Date: Fri, 09 May 2014 12:36:00 -0000	[thread overview]
Message-ID: <bug-61114-4-r0Gmty9ST1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61114-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Tejas Belagod <belagod at gcc dot gnu.org> ---
So, does that mean the folded value 120 is in the wrong place? The fix that I'm
testing swaps the first and last elements of the const vector {120, 0, 0, 0}.

PS: Sorry, my statement "The final folded value is extracted from the LSB which
are bits 32:96 on BE systems" should have read "The final folded value is
extracted from the LSB which are bits 96..127 on BE systems" if that caused
confusion.


  parent reply	other threads:[~2014-05-09 12:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-61114-4@http.gcc.gnu.org/bugzilla/>
2014-05-08 15:44 ` belagod at gcc dot gnu.org
2014-05-09 11:19 ` rguenth at gcc dot gnu.org
2014-05-09 12:29 ` belagod at gcc dot gnu.org
2014-05-09 12:33 ` rguenther at suse dot de
2014-05-09 12:36 ` belagod at gcc dot gnu.org [this message]
2014-05-09 12:53 ` rguenth at gcc dot gnu.org
2014-05-09 12:55 ` rguenth at gcc dot gnu.org
2014-07-29 16:04 ` alan.lawrence at arm dot com
2014-10-27 14:21 ` alalaw01 at gcc dot gnu.org
2014-10-27 14:45 ` alalaw01 at gcc dot gnu.org
2014-10-28 10:46 ` ramana at gcc dot gnu.org
2015-02-10  2:24 ` collison at gcc dot gnu.org
2015-03-29 14:34 ` mikpelinux at gmail dot com
2015-03-30 10:40 ` rguenth 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-61114-4-r0Gmty9ST1@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).