public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rakdver at atrey dot karlin dot mff dot cuni dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/16001] [3.5 Regression] unable to find a register to spill in class `AREG' (-O2 -funroll-loops)
Date: Wed, 30 Jun 2004 15:00:00 -0000 [thread overview]
Message-ID: <20040630145542.9870.qmail@sourceware.org> (raw)
In-Reply-To: <20040615150450.16001.rguenth@tat.physik.uni-tuebingen.de>
------- Additional Comments From rakdver at atrey dot karlin dot mff dot cuni dot cz 2004-06-30 14:55 -------
Subject: Re: [3.5 Regression] unable to find a register to spill in class `AREG' (-O2 -funroll-loops)
Hello,
> It seems to be fixed on both lno and mainline as of today (Jun30) - but I cannot
> find traces of the patch that went into lno on mainline.
>
> Is the patch still needed on mainline?
yes, the patch is still needed, even if the problem was masked by some
other commit.
Zdenek
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16001
next prev parent reply other threads:[~2004-06-30 14:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 15:05 [Bug tree-optimization/16001] New: " rguenth at tat dot physik dot uni-tuebingen dot de
2004-06-15 15:56 ` [Bug rtl-optimization/16001] " pinskia at gcc dot gnu dot org
2004-06-15 23:45 ` rakdver at gcc dot gnu dot org
2004-06-15 23:46 ` rakdver at gcc dot gnu dot org
2004-06-16 7:47 ` reichelt at gcc dot gnu dot org
2004-06-16 15:18 ` reichelt at gcc dot gnu dot org
2004-06-21 11:18 ` [Bug rtl-optimization/16001] [3.5? Regression] " belyshev at lubercy dot com
2004-06-21 16:41 ` pinskia at gcc dot gnu dot org
2004-06-21 18:22 ` [Bug rtl-optimization/16001] [3.5 " belyshev at lubercy dot com
2004-06-21 19:18 ` rakdver at gcc dot gnu dot org
2004-06-21 19:24 ` cvs-commit at gcc dot gnu dot org
2004-06-23 15:55 ` reichelt at gcc dot gnu dot org
2004-06-30 13:29 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-06-30 13:48 ` giovannibajo at libero dot it
2004-06-30 15:00 ` rakdver at atrey dot karlin dot mff dot cuni dot cz [this message]
2004-07-01 8:33 ` reichelt at gcc dot gnu dot org
2004-07-01 8:34 ` reichelt at gcc dot gnu dot org
2004-07-11 2:53 ` rakdver at gcc dot gnu dot org
2004-07-11 2:53 ` cvs-commit 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=20040630145542.9870.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).