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/52573] [4.6/4.7/4.8 regression] regrename creates overlapping register allocations for output operands
Date: Fri, 07 Dec 2012 13:39:00 -0000	[thread overview]
Message-ID: <bug-52573-4-VDTBeZBmdf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52573-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #7 from Kenneth Zadeck <zadeck at naturalbridge dot com> 2012-12-07 13:39:10 UTC ---
alexandre,

when we did the dataflow stuff, my expertise was primarily in deciding which
problems could be applied to which of the passes and how and when to actually
(re)solve the equations.    i left most of the scanning of the actual rtl to
people like stevenb, richard sandiford, bonzini and dannyb.  This question is
really beyond my level of rtl expertise and i would get one of the first three
involved if i were you.

sorry

kenny


  parent reply	other threads:[~2012-12-07 13:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 23:50 [Bug rtl-optimization/52573] New: [4.5/4.6/4.7/4.8 " schwab@linux-m68k.org
2012-03-13  8:30 ` [Bug rtl-optimization/52573] " rguenth at gcc dot gnu.org
2012-03-14 10:47 ` schwab@linux-m68k.org
2012-04-13 12:59 ` rguenth at gcc dot gnu.org
2012-04-13 13:02 ` bernds at gcc dot gnu.org
2012-06-10 20:29 ` mikpe at it dot uu.se
2012-07-02 11:32 ` rguenth at gcc dot gnu.org
2012-12-07  0:14 ` [Bug rtl-optimization/52573] [4.6/4.7/4.8 " aoliva at gcc dot gnu.org
2012-12-07 11:17 ` aoliva at gcc dot gnu.org
2012-12-07 13:39 ` zadeck at naturalbridge dot com [this message]
2012-12-07 16:46 ` schwab@linux-m68k.org
2012-12-08 19:06 ` mikpe at it dot uu.se
2012-12-08 19:32 ` schwab@linux-m68k.org
2013-01-16  4:57 ` law at redhat dot com
2013-01-16 20:40 ` schwab@linux-m68k.org
2013-01-18  7:55 ` law at gcc dot gnu.org
2013-01-18  7:56 ` law at redhat dot com
2013-01-24  9:38 ` jakub 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-52573-4-VDTBeZBmdf@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).