public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/44031] [4.4/4.5 Regression] ice in subst_reloads, at reload.c:6327
Date: Wed, 26 Jan 2011 22:45:00 -0000	[thread overview]
Message-ID: <bug-44031-4-H9r9UuZzBm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44031-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Jeffrey A. Law <law at redhat dot com> 2011-01-26 22:11:55 UTC ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/26/11 11:14, ebotcazou at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44031
> 
> Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |ebotcazou at gcc dot
>                    |                            |gnu.org
>       Known to work|                            |4.6.0
>    Target Milestone|4.6.0                       |4.4.6
>             Summary|[4.4/4.5/4.6 Regression]    |[4.4/4.5 Regression] ice in
>                    |ice in subst_reloads, at    |subst_reloads, at
>                    |reload.c:6327               |reload.c:6327
>       Known to fail|                            |4.5.3
> 
> --- Comment #7 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-01-26 18:13:17 UTC ---
> Works on the mainline, still fails on the 4.5 branch.
FWIW, I have no idea which change might have fixed it on the trunk; more
likely than not it was by accident rather than by design.  As such I
doubt there's a particular patch that could be pulled from the trunk and
applied to the 4.5 branch to resolve this issue.

jeff

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNQJwdAAoJEBRtltQi2kC7XRoH/RSyn/+awVJ01vTwYqGu/lZm
fRED3JruXqXvg7KH2xdbL9I/BEHczNvC3YzjFJvb+RjD1MxHt4+7AmPkMMkJJPPu
NoPL5iNGitLfok2Sy2YNgOKEr7t6MW0fpbcpmhx2tRk7tySsm6iWlo1Yh0ruu4rH
XDROh1n8oRE1V+ERFlYhJtc6sqnu4Ma1nHQ57pZeUvd53VSCHpnKF/E3hsDUyh5O
gwkWN0E+zgREQnxGGMGqbcS4BuUHwvVdsCtvVb9SSWkdbwXdPtAdxH0c/7Irbh0E
iBYU/8oTh9RY/Q6fbZfNnJn1YVGGWNHEbFRYP32ZriazIAwjHHbky79i6CuHgSE=
=Zwj2
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2011-01-26 22:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-44031-4@http.gcc.gnu.org/bugzilla/>
2011-01-26 18:28 ` ebotcazou at gcc dot gnu.org
2011-01-26 22:45 ` law at redhat dot com [this message]
2011-01-28 15:19 ` mikpe at it dot uu.se
2011-01-28 18:59 ` mikpe at it dot uu.se
2011-01-28 19:37 ` law at redhat dot com
2011-01-28 19:39 ` law at redhat dot com
2011-01-31 11:03 ` [Bug rtl-optimization/44031] " ebotcazou at gcc dot gnu.org
2011-02-02 18:24 ` dnovillo 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-44031-4-H9r9UuZzBm@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).