public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38621] [4.6/4.7/4.8 Regression] sh gcc unable to spill register when building ghostscript-gpl with -O2
Date: Mon, 16 Jul 2012 22:25:00 -0000	[thread overview]
Message-ID: <bug-38621-4-5fqF54Zvat@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-38621-4@http.gcc.gnu.org/bugzilla/>

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

Oleg Endo <olegendo at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |olegendo at gcc dot gnu.org
      Known to work|                            |4.6.4, 4.7.2
      Known to fail|                            |

--- Comment #10 from Oleg Endo <olegendo at gcc dot gnu.org> 2012-07-16 22:24:11 UTC ---
I've tried to reproduce the issue with rev 189549 (GCC 4.8),
GCC 4.7.2 20120711 (prerelease) and GCC 4.6.4 20120716 (prerelease).
It seems this is no longer an issue.


  parent reply	other threads:[~2012-07-16 22:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-38621-4@http.gcc.gnu.org/bugzilla/>
2011-06-27 13:43 ` [Bug target/38621] [4.3/4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-03-13 13:53 ` [Bug target/38621] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org
2012-07-02 13:46 ` [Bug target/38621] [4.6/4.7/4.8 " rguenth at gcc dot gnu.org
2012-07-16 22:25 ` olegendo at gcc dot gnu.org [this message]
2012-07-18  1:12 ` kkojima at gcc dot gnu.org
2012-07-18  7:58 ` olegendo at gcc dot gnu.org
2012-07-18 18:58 ` olegendo 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-38621-4-5fqF54Zvat@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).