public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/24319] [4.3/4.4/4.5 regression] amd64 register spill error with -fschedule-insns
Date: Tue, 31 Mar 2009 18:58:00 -0000	[thread overview]
Message-ID: <20090331185824.3587.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24319-11506@http.gcc.gnu.org/bugzilla/>



------- Comment #13 from jsm28 at gcc dot gnu dot org  2009-03-31 18:58 -------
Closing 4.2 branch.


-- 

jsm28 at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[4.2/4.3/4.4/4.5 regression]|[4.3/4.4/4.5 regression]
                   |amd64 register spill error  |amd64 register spill error
                   |with -fschedule-insns       |with -fschedule-insns
   Target Milestone|4.2.5                       |4.3.4


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


  parent reply	other threads:[~2009-03-31 18:58 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-11 20:48 [Bug c/24319] New: " erg at trifocus dot net
2005-10-11 20:49 ` [Bug c/24319] " erg at trifocus dot net
2005-10-11 20:51 ` [Bug target/24319] " pinskia at gcc dot gnu dot org
2005-10-11 21:07 ` belyshev at depni dot sinp dot msu dot ru
2005-10-11 23:18 ` [Bug rtl-optimization/24319] [3.4/4.0/4.1 regression] " belyshev at depni dot sinp dot msu dot ru
2005-10-11 23:43 ` pinskia at gcc dot gnu dot org
2005-10-30 23:22 ` pinskia at gcc dot gnu dot org
2005-11-09 15:27 ` uros at kss-loka dot si
2005-11-09 21:07 ` wilson at tuliptree dot org
2006-02-28 20:41 ` [Bug rtl-optimization/24319] [3.4/4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org
2006-05-25  2:46 ` [Bug rtl-optimization/24319] [4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org
2007-02-14  9:39 ` [Bug rtl-optimization/24319] [4.0/4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org
2007-10-11 10:32 ` ubizjak at gmail dot com
2008-07-04 20:06 ` [Bug rtl-optimization/24319] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2009-03-20 19:36 ` steven at gcc dot gnu dot org
2009-03-23 17:04 ` vmakarov at redhat dot com
2009-03-31 18:58 ` jsm28 at gcc dot gnu dot org [this message]
2009-08-04 12:34 ` [Bug rtl-optimization/24319] [4.3/4.4/4.5 " rguenth at gcc dot gnu dot org
2009-08-27 17:33 ` ubizjak at gmail dot com
2009-08-28 16:54 ` lucier at math dot purdue dot edu
2009-09-01 12:08 ` ubizjak at gmail dot com
2009-09-02  2:54 ` lucier at math dot purdue dot edu
2009-09-02 16:15 ` vmakarov at redhat dot com
2009-09-02 16:52 ` lucier at math dot purdue dot edu
2009-09-02 17:11 ` vmakarov at redhat dot com
2009-09-02 17:24 ` lucier at math dot purdue dot edu
2009-09-03 18:05 ` lucier at math dot purdue dot edu
2009-10-01  6:56 ` pinskia at gcc dot gnu dot org
2010-02-02 18:02 ` spop at gcc dot gnu dot org
2010-02-02 18:07 ` steven at gcc dot gnu dot org
2010-02-03  6:20 ` [Bug rtl-optimization/24319] [4.3/4.4 " spop at gcc dot gnu dot org
2010-05-22 18:36 ` rguenth 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=20090331185824.3587.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).