public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zadeck at naturalbridge dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/35404] ra-conflict does not handle subregs optimally
Date: Fri, 25 Apr 2008 21:35:00 -0000	[thread overview]
Message-ID: <20080425213440.6520.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35404-1313@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from zadeck at naturalbridge dot com  2008-04-25 21:34 -------
any regressions, if any exist at all, must be addressed by vlad's new register
allocator.


-- 

zadeck at naturalbridge dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vmakarov at gcc dot gnu dot
                   |                            |org
         AssignedTo|zadeck at naturalbridge dot |vmakarov at gcc dot gnu dot
                   |com                         |org
             Status|NEW                         |ASSIGNED


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


  parent reply	other threads:[~2008-04-25 21:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 22:59 [Bug rtl-optimization/35404] New: " ian at airs dot com
2008-02-28 22:59 ` [Bug rtl-optimization/35404] " ian at airs dot com
2008-02-29 18:44 ` ian at airs dot com
2008-03-10 21:49 ` steven at gcc dot gnu dot org
2008-04-13 19:15 ` hutchinsonandy at gcc dot gnu dot org
2008-04-13 19:32 ` zadeck at naturalbridge dot com
2008-04-13 19:48 ` hutchinsonandy at gcc dot gnu dot org
2008-04-25 21:35 ` zadeck at naturalbridge dot com [this message]
2009-08-27 20:29 ` aldot at gcc dot gnu dot 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=20080425213440.6520.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).