From: Eric Botcazou <ebotcazou@adacore.com>
To: bonzini@gnu.org
Cc: gcc-patches@gcc.gnu.org, Mark Mitchell <mark@codesourcery.com>
Subject: Re: PR/32004, tree-ssa caused in/out asm constraints to often need reloads
Date: Sat, 07 Jul 2007 16:29:00 -0000 [thread overview]
Message-ID: <200707071702.30366.ebotcazou@adacore.com> (raw)
In-Reply-To: <468CC82F.2060702@lu.unisi.ch>
> Bootstrapped/regtested i686-pc-linux-gnu with no new failure and fixing
> pr21291.c, ok for 4.2/4.3?
AFAICS you didn't request approval for the 4.1 branch, but nevertheless
installed the patch on this branch too. Now I get with RTL checking on:
FAIL: gcc.dg/torture/pr20314-1.c -O1 (internal compiler error)
FAIL: gcc.dg/torture/pr20314-1.c -O1 (test for excess errors)
FAIL: gcc.dg/torture/pr20314-1.c -O2 (internal compiler error)
FAIL: gcc.dg/torture/pr20314-1.c -O2 (test for excess errors)
FAIL: gcc.dg/torture/pr20314-1.c -O3 -fomit-frame-pointer (internal compiler
error)
FAIL: gcc.dg/torture/pr20314-1.c -O3 -fomit-frame-pointer (test for excess
errors)
FAIL: gcc.dg/torture/pr20314-1.c -O3 -g (internal compiler error)
FAIL: gcc.dg/torture/pr20314-1.c -O3 -g (test for excess errors)
FAIL: gcc.dg/torture/pr20314-1.c -Os (internal compiler error)
FAIL: gcc.dg/torture/pr20314-1.c -Os (test for excess errors)
Executing on host: /home/eric/gnat/gnat6_41/native32/gcc/xgcc
-B/home/eric/gnat/gnat6_41/native32/gcc/ /home/eric/gnat/gnat6_41/src/gcc/testsuite/gcc.dg/torture/pr20314-1.c
-O0 -fno-show-column -S -o pr20314-1.s (timeout = 300)
PASS: gcc.dg/torture/pr20314-1.c -O0 (test for excess errors)
Executing on host: /home/eric/gnat/gnat6_41/native32/gcc/xgcc
-B/home/eric/gnat/gnat6_41/native32/gcc/ /home/eric/gnat/gnat6_41/src/gcc/testsuite/gcc.dg/torture/pr20314-1.c
-O1 -fno-show-column -S -o pr20314-1.s (timeout = 300)
/home/eric/gnat/gnat6_41/src/gcc/testsuite/gcc.dg/torture/pr20314-1.c: In
function 'f3':
/home/eric/gnat/gnat6_41/src/gcc/testsuite/gcc.dg/torture/pr20314-1.c:29:
internal compiler error: RTL check: access of elt 1 of 'const_int' with last
elt 0 in update_equiv_regs, at local-alloc.c:1117
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:mailto:report@adacore.com> for instructions.
compiler exited with status 1
Please revert the patch on the 4.1 branch.
--
Eric Botcazou
next prev parent reply other threads:[~2007-07-07 14:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 10:54 Paolo Bonzini
[not found] ` <84fc9c000707050401h46157b0fye4b32c3e6b1c8063@mail.gmail.com>
2007-07-05 11:48 ` Paolo Bonzini
2007-07-05 18:34 ` Mark Mitchell
2007-07-05 19:39 ` Paolo Bonzini
2007-07-05 20:24 ` Mark Mitchell
2007-07-05 20:15 ` Paolo Bonzini
2007-07-07 16:29 ` Eric Botcazou [this message]
2007-07-07 18:24 ` Andrew Pinski
2007-07-07 18:30 ` Eric Botcazou
2007-07-09 2:23 ` Paolo Bonzini
2007-07-09 6:52 ` Eric Botcazou
2007-07-09 12:09 ` Paolo Bonzini
2007-07-09 12:32 ` Paolo Bonzini
2007-07-09 12:40 ` Richard Guenther
2007-07-09 13:01 ` Eric Botcazou
2007-07-09 13:01 ` Richard Guenther
2007-07-09 13:36 ` Eric Botcazou
2007-07-09 13:12 ` Paolo Bonzini
2007-07-09 13:23 ` Andrew Pinski
2007-07-09 13:45 ` Eric Botcazou
2007-07-09 15:33 ` Paolo Bonzini
2007-07-09 17:25 ` Eric Botcazou
2007-07-09 14:00 ` Eric Botcazou
2007-07-13 9:48 ` Paolo Bonzini
2007-07-13 13:42 ` Eric Botcazou
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=200707071702.30366.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mark@codesourcery.com \
/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).