public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tony dot linthicum at amd dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/15792] missed subreg optimization
Date: Mon, 06 Feb 2006 17:13:00 -0000	[thread overview]
Message-ID: <20060206171308.26961.qmail@sourceware.org> (raw)
In-Reply-To: <bug-15792-6528@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from tony dot linthicum at amd dot com  2006-02-06 17:13 -------
So do I, at least for the original code (i.e. test and test1).  I'm curious,
though, if you've tried the example that I listed above (foo).  I still get
subregs with that one, though I honestly don't recall at the moment whether or
not it makes the register allocator screw up or not (I *think* it does, but I'd
have to check).  Either way, though, the presence of the subregs provides the
needed fodder for RA badness so I'm curious if it's present in what you're
working on.


-- 


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


  parent reply	other threads:[~2006-02-06 17:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-15792-6528@http.gcc.gnu.org/bugzilla/>
2006-01-18  4:45 ` pinskia at gcc dot gnu dot org
2006-01-20 15:48 ` tony dot linthicum at amd dot com
2006-01-20 15:52 ` pinskia at gcc dot gnu dot org
2006-02-02 18:18 ` ian at airs dot com
2006-02-06 17:13 ` tony dot linthicum at amd dot com [this message]
2006-02-07  0:30 ` ian at airs dot com
2006-02-07  8:23 ` ian at airs dot com
2007-11-10  0:15 ` rask at gcc dot gnu dot org
     [not found] <bug-15792-4@http.gcc.gnu.org/bugzilla/>
2021-10-15  3:00 ` gabravier at gmail dot com
2023-05-15  5:34 ` pinskia at gcc dot gnu.org
2004-06-03  4:27 [Bug rtl-optimization/15792] New: " pinskia at gcc dot gnu dot org
2004-06-15 20:07 ` [Bug rtl-optimization/15792] " bangerth at dealii dot org
2004-08-20 18:47 ` dann at godzilla dot ics dot uci dot edu

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=20060206171308.26961.qmail@sourceware.org \
    --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).