public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/33642] unrecognizable insn for -frtl-abstract-sequences
Date: Thu, 03 Apr 2008 17:05:00 -0000 [thread overview]
Message-ID: <20080403170441.3036.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33642-4503@http.gcc.gnu.org/bugzilla/>
------- Comment #21 from janis at gcc dot gnu dot org 2008-04-03 17:04 -------
Dominique, in answer to your question in comment #19, without the patch any
code for powerpc*-linux gets an ICE as reported originally. The very long
compilation times are a concern, but wrong code in four CPU2000 tests is much
worse. With the patch, tests vpr and crafty pass with "-m32 -Os
-frtl-abstract-sequences", but with "-m64 -Os -frtl-abstract-sequences test gcc
fails at runtime and test gap hangs at runtime.
I'm providing this information to let the developers know that the patch isn't
ready. I can test later versions. I don't have time, however, to minimize
runtime failures in SPEC tests to help pinpoint the problems.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33642
next prev parent reply other threads:[~2008-04-03 17:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 17:09 [Bug rtl-optimization/33642] New: " janis at gcc dot gnu dot org
2007-10-03 21:02 ` [Bug rtl-optimization/33642] " rguenth at gcc dot gnu dot org
2008-03-03 13:52 ` loki at gcc dot gnu dot org
2008-03-05 11:09 ` loki at gcc dot gnu dot org
2008-03-06 15:02 ` loki at gcc dot gnu dot org
2008-03-06 18:21 ` dominiq at lps dot ens dot fr
2008-03-06 19:19 ` dominiq at lps dot ens dot fr
2008-03-08 17:15 ` dje at gcc dot gnu dot org
2008-03-08 21:04 ` dje at gcc dot gnu dot org
2008-03-09 21:55 ` danglin at gcc dot gnu dot org
2008-03-11 9:46 ` loki at gcc dot gnu dot org
2008-03-11 14:35 ` dominiq at lps dot ens dot fr
2008-03-13 18:02 ` joel at gcc dot gnu dot org
2008-03-14 8:31 ` loki at gcc dot gnu dot org
2008-03-30 19:31 ` dje at gcc dot gnu dot org
2008-03-30 22:40 ` eric dot weddington at atmel dot com
2008-03-31 10:13 ` dominiq at lps dot ens dot fr
2008-04-02 22:11 ` janis at gcc dot gnu dot org
2008-04-03 8:25 ` loki at gcc dot gnu dot org
2008-04-03 15:05 ` dominiq at lps dot ens dot fr
2008-04-03 15:22 ` dominiq at lps dot ens dot fr
2008-04-03 17:05 ` janis at gcc dot gnu dot org [this message]
2008-05-09 18:37 ` aldot at gcc dot gnu dot org
2008-05-10 12:02 ` rsandifo at gcc dot gnu dot org
2008-05-10 12:04 ` rsandifo at gcc dot gnu dot org
2008-05-15 7:58 ` aldot at gcc dot gnu dot org
2008-05-25 17:30 ` ghazi at gcc dot gnu dot org
2008-07-21 1:39 ` hp at gcc dot gnu dot org
2008-09-20 19:18 ` ebotcazou at gcc dot gnu dot org
2008-09-21 22:40 ` kkojima at gcc dot gnu dot org
2008-09-22 15:18 ` dje at gcc dot gnu dot org
2008-10-29 23:34 ` jakub at gcc dot gnu dot org
2008-12-01 15:22 ` uros at gcc dot gnu dot org
2009-11-29 16:13 ` ghazi at gcc dot gnu dot org
2009-11-29 16:35 ` 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=20080403170441.3036.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).