public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/61306] [4.10 Regression] wrong code at -Os and above on x86_64-linux-gnu
Date: Mon, 26 May 2014 12:22:00 -0000	[thread overview]
Message-ID: <bug-61306-4-7wfAkaCIQC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61306-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61306

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
16 bit load in host endianness found at: b.3_7 = (int) load_dst_10;

at least the dumping is confusing as well ;)

But the issue seems to be that we are missing that a.0_2 and c.1_3
sign-extend.

  a.0_2 = a;
  c.1_3 = (char) a.0_2;
  c = c.1_3;
  _5 = (int) a.0_2;
  _6 = (int) c.1_3;
  b.3_7 = _6 | _5;


  parent reply	other threads:[~2014-05-26 12:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-25  2:58 [Bug tree-optimization/61306] New: " su at cs dot ucdavis.edu
2014-05-26 12:20 ` [Bug tree-optimization/61306] [4.10 Regression] " rguenth at gcc dot gnu.org
2014-05-26 12:22 ` rguenth at gcc dot gnu.org [this message]
2014-05-27  5:50 ` thomas.preudhomme at arm dot com
2014-05-28 11:47 ` thomas.preudhomme at arm dot com
2014-05-30  6:40 ` thomas.preudhomme at arm dot com
2014-06-11 10:05 ` thopre01 at gcc dot gnu.org
2014-06-11 10:06 ` thopre01 at gcc dot gnu.org
2014-06-30  1:59 ` thopre01 at gcc dot gnu.org
2014-06-30  2:12 ` thopre01 at gcc dot gnu.org
2014-07-03 21:45 ` olegendo at gcc dot gnu.org
2014-07-04  4:41 ` thopre01 at gcc dot gnu.org
2014-11-19 13:39 ` [Bug tree-optimization/61306] [5 " 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-61306-4-7wfAkaCIQC@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).