public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52055] load of 64-bit pointer reads 64 bits even when only 32 are used
Date: Wed, 01 Feb 2012 16:14:00 -0000	[thread overview]
Message-ID: <bug-52055-4-C6AIL0TcGY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52055-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-02-01 16:13:43 UTC ---
> So, shell we do this kind of shortening in fwprop instead?  If a MEM load has
> all uses subregged to a narrower mode, try to subreg it and adjust the callers?

This would be backward combining (a la REE) though, not forward propagating.


  parent reply	other threads:[~2012-02-01 16:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 19:28 [Bug target/52055] New: " jhaberman at gmail dot com
2012-01-31 11:44 ` [Bug target/52055] " rguenth at gcc dot gnu.org
2012-01-31 18:29 ` jhaberman at gmail dot com
2012-01-31 19:02 ` jakub at gcc dot gnu.org
2012-02-01 16:14 ` ebotcazou at gcc dot gnu.org [this message]
2012-02-01 16:36 ` jakub at gcc dot gnu.org
2012-02-14  5:22 ` pinskia 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-52055-4-C6AIL0TcGY@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).