From: Richard Sandiford <rsandifo@nildram.co.uk>
To: "Richard Guenther" <richard.guenther@gmail.com>
Cc: "Alexandre Oliva" <aoliva@redhat.com>,
"Roman Zippel" <zippel@linux-m68k.org>,
"Bernd Schmidt" <bernds_cb1@t-online.de>,
"Diego Novillo" <dnovillo@acm.org>,
"Daniel Berlin" <dberlin@dberlin.org>,
"GCC Patches" <gcc-patches@gcc.gnu.org>,
"Andrew Pinski" <pinskia@gmail.com>,
"Eric Botcazou" <ebotcazou@adacore.com>
Subject: Re: SRA bit-field optimization
Date: Wed, 03 Oct 2007 08:38:00 -0000 [thread overview]
Message-ID: <87tzp8twxh.fsf@firetop.home> (raw)
In-Reply-To: <84fc9c000710021015p4276c5d2s70c75e13a2225f30@mail.gmail.com> (Richard Guenther's message of "Tue\, 2 Oct 2007 19\:15\:31 +0200")
"Richard Guenther" <richard.guenther@gmail.com> writes:
> On 9/28/07, Alexandre Oliva <aoliva@redhat.com> wrote:
>> On Aug 24, 2007, Alexandre Oliva <aoliva@redhat.com> wrote:
>>
>> > On Jul 6, 2007, Alexandre Oliva <aoliva@redhat.com> wrote:
>> >> Here's the patch, bootstrapped and regression-tested on
>> >> x86_64-linux-gnu and i686-pc-linux-gnu (with an oldish, pre-sccvn
>> >> tree, to be able to test ada as well). Tests on ppc-linux-gnu and
>> >> ppc64-linux-gnu underway.
>>
>> >> Ok to install?
>>
>> > Ping?
>>
>> Ping^2?
>>
>> Tests on ppc* passed back then, BTW.
>
> It seems this was committed now, and causes ncurses build to fail on
> x86_64:
>
> ../ncurses/./base/lib_addch.c: In function 'render_char':
> ../ncurses/./base/lib_addch.c:541: internal compiler error: in
> bitfield_overlaps_p, at tree-sra.c:2901
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://bugs.opensuse.org/> for instructions.
> make[1]: *** [../obj_s/lib_addch.o] Error 1
>
> I'll file a bugreport once I get hands on preprocessed source.
For the record, it also causes many failures on mips-linux-gnu,
such as the following execute.exp ones:
FAIL: gcc.c-torture/execute/20000113-1.c execution, -O1
FAIL: gcc.c-torture/execute/20000113-1.c execution, -O2
FAIL: gcc.c-torture/execute/20000113-1.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/20000113-1.c execution, -O3 -g
FAIL: gcc.c-torture/execute/20000113-1.c execution, -Os
FAIL: gcc.c-torture/execute/20031211-1.c execution, -O1
FAIL: gcc.c-torture/execute/20031211-1.c execution, -O2
FAIL: gcc.c-torture/execute/20031211-1.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/20031211-1.c execution, -O3 -g
FAIL: gcc.c-torture/execute/20031211-1.c execution, -Os
FAIL: gcc.c-torture/execute/20031211-2.c execution, -O1
FAIL: gcc.c-torture/execute/20031211-2.c execution, -O2
FAIL: gcc.c-torture/execute/20031211-2.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/20031211-2.c execution, -O3 -g
FAIL: gcc.c-torture/execute/20031211-2.c execution, -Os
FAIL: gcc.c-torture/execute/20040307-1.c execution, -O1
FAIL: gcc.c-torture/execute/20040307-1.c execution, -O2
FAIL: gcc.c-torture/execute/20040307-1.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/20040307-1.c execution, -O3 -fomit-frame-pointer -funroll-loops
FAIL: gcc.c-torture/execute/20040307-1.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/20040307-1.c execution, -O3 -g
FAIL: gcc.c-torture/execute/20040307-1.c execution, -Os
FAIL: gcc.c-torture/execute/20040709-1.c execution, -O1
FAIL: gcc.c-torture/execute/20040709-1.c execution, -O2
FAIL: gcc.c-torture/execute/20040709-1.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/20040709-1.c execution, -O3 -fomit-frame-pointer -funroll-loops
FAIL: gcc.c-torture/execute/20040709-1.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/20040709-1.c execution, -O3 -g
FAIL: gcc.c-torture/execute/20040709-1.c execution, -Os
FAIL: gcc.c-torture/execute/20040709-2.c execution, -O1
FAIL: gcc.c-torture/execute/20040709-2.c execution, -O2
FAIL: gcc.c-torture/execute/20040709-2.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/20040709-2.c execution, -O3 -fomit-frame-pointer -funroll-loops
FAIL: gcc.c-torture/execute/20040709-2.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/20040709-2.c execution, -O3 -g
FAIL: gcc.c-torture/execute/20040709-2.c execution, -Os
FAIL: gcc.c-torture/execute/920908-2.c execution, -O1
FAIL: gcc.c-torture/execute/920908-2.c execution, -O2
FAIL: gcc.c-torture/execute/920908-2.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/920908-2.c execution, -O3 -g
FAIL: gcc.c-torture/execute/920908-2.c execution, -Os
FAIL: gcc.c-torture/execute/bf64-1.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/bf64-1.c execution, -O3 -g
FAIL: gcc.c-torture/execute/bitfld-1.c execution, -O1
FAIL: gcc.c-torture/execute/bitfld-1.c execution, -O2
FAIL: gcc.c-torture/execute/bitfld-1.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/bitfld-1.c execution, -O3 -g
FAIL: gcc.c-torture/execute/bitfld-1.c execution, -Os
FAIL: gcc.c-torture/execute/compndlit-1.c execution, -O1
FAIL: gcc.c-torture/execute/compndlit-1.c execution, -O2
FAIL: gcc.c-torture/execute/compndlit-1.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/compndlit-1.c execution, -O3 -g
FAIL: gcc.c-torture/execute/compndlit-1.c execution, -Os
FWIW, the gcc.c-torture/execute/20000113-1.c failures can easily be
reproduced with a cross-compiler, because after the patch, foobar is
optimised to a call to abort.
Richard
next prev parent reply other threads:[~2007-10-03 8:38 UTC|newest]
Thread overview: 104+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 0:29 Reload bug & SRA oddness Bernd Schmidt
2007-04-20 3:19 ` Andrew Pinski
2007-04-20 3:53 ` Daniel Berlin
2007-04-20 4:30 ` Bernd Schmidt
2007-04-20 4:48 ` Andrew Pinski
2007-04-20 7:32 ` Alexandre Oliva
2007-04-20 12:57 ` Bernd Schmidt
2007-04-20 18:28 ` Alexandre Oliva
2007-04-20 18:40 ` Alexandre Oliva
2007-04-30 10:09 ` Bernd Schmidt
2007-04-30 19:04 ` Alexandre Oliva
2007-04-30 19:08 ` Alexandre Oliva
2007-05-01 15:38 ` Alexandre Oliva
2007-05-01 15:45 ` Eric Botcazou
2007-05-04 0:19 ` Alexandre Oliva
2007-05-01 15:53 ` Diego Novillo
2007-05-01 16:03 ` Eric Botcazou
2007-05-01 16:51 ` Arnaud Charlet
2007-05-01 16:54 ` Arnaud Charlet
2007-05-01 17:31 ` Andreas Schwab
2007-05-01 16:24 ` Roman Zippel
2007-05-04 4:07 ` Alexandre Oliva
2007-05-04 5:24 ` Alexandre Oliva
2007-05-05 18:19 ` Roman Zippel
2007-05-06 5:13 ` Alexandre Oliva
2007-05-06 12:13 ` Bernd Schmidt
2007-05-06 14:27 ` Alexandre Oliva
2007-05-06 15:01 ` Alexandre Oliva
2007-05-06 23:44 ` Alexandre Oliva
2007-05-06 23:51 ` Diego Novillo
2007-05-07 0:14 ` Alexandre Oliva
2007-05-07 2:21 ` Andrew Pinski
2007-05-09 12:25 ` Bernd Schmidt
2007-05-10 7:47 ` Alexandre Oliva
2007-05-10 11:00 ` Bernd Schmidt
2007-05-22 7:09 ` Alexandre Oliva
2007-05-22 17:34 ` Roman Zippel
2007-05-22 20:49 ` Alexandre Oliva
2007-05-23 13:07 ` Roman Zippel
2007-05-22 21:23 ` Alexandre Oliva
2007-05-09 18:32 ` Roman Zippel
2007-05-10 7:49 ` Alexandre Oliva
2007-05-15 17:39 ` Alexandre Oliva
2007-05-17 21:17 ` Andrew Pinski
2007-05-28 10:49 ` Bernd Schmidt
2007-05-31 20:57 ` Alexandre Oliva
2007-06-02 17:41 ` Bernd Schmidt
2007-06-06 3:18 ` Alexandre Oliva
2007-06-25 18:48 ` Alexandre Oliva
2007-06-26 23:01 ` Bernd Schmidt
2007-06-28 4:50 ` Alexandre Oliva
2007-07-03 0:52 ` Roman Zippel
2007-07-06 9:21 ` Alexandre Oliva
2007-08-24 7:28 ` SRA bit-field optimization (was: Re: Reload bug & SRA oddness) Alexandre Oliva
2007-09-28 9:17 ` SRA bit-field optimization Alexandre Oliva
2007-10-02 17:15 ` Richard Guenther
2007-10-03 8:38 ` Richard Sandiford [this message]
2007-10-03 16:50 ` Alexandre Oliva
2007-10-03 18:23 ` Richard Sandiford
2007-10-04 19:56 ` Richard Sandiford
2007-10-05 17:43 ` Alexandre Oliva
2007-10-06 8:02 ` Richard Sandiford
2007-10-06 21:06 ` John David Anglin
2007-10-06 22:12 ` Richard Sandiford
2007-10-07 23:44 ` Alexandre Oliva
2007-10-08 21:14 ` John David Anglin
2007-10-08 23:51 ` Alexandre Oliva
2007-10-09 0:31 ` John David Anglin
2007-10-09 4:41 ` Alexandre Oliva
2007-10-09 4:45 ` Alexandre Oliva
2007-10-06 16:01 ` David Daney
2007-10-03 14:37 ` Daniel Berlin
2007-10-03 14:44 ` Diego Novillo
2007-10-05 15:03 ` Richard Guenther
2007-10-05 16:20 ` Alexandre Oliva
2007-10-05 16:24 ` Richard Guenther
2007-10-05 16:26 ` Diego Novillo
2007-10-05 20:08 ` Alexandre Oliva
2007-10-09 4:55 ` Alexandre Oliva
2007-10-03 7:45 ` Eric Botcazou
2007-10-03 21:36 ` Eric Botcazou
2007-10-08 20:28 ` Alexandre Oliva
2007-10-05 6:24 ` Eric Botcazou
2007-10-05 16:03 ` Alexandre Oliva
2007-10-07 9:01 ` Eric Botcazou
2007-10-07 23:58 ` Alexandre Oliva
2007-10-08 5:13 ` Eric Botcazou
2007-10-08 20:29 ` Alexandre Oliva
2007-10-08 21:00 ` Eric Botcazou
2007-10-08 23:56 ` Alexandre Oliva
2007-09-29 17:52 ` Reload bug & SRA oddness Diego Novillo
2007-04-20 17:07 ` Daniel Berlin
2007-04-28 20:48 ` Bernd Schmidt
2007-04-28 21:26 ` Richard Guenther
2007-04-28 21:49 ` Daniel Berlin
2007-04-29 10:04 ` Richard Guenther
2007-04-29 10:27 ` Richard Guenther
2007-04-29 10:31 ` Richard Guenther
2007-04-29 11:16 ` Richard Guenther
2007-04-20 14:01 ` Bernd Schmidt
2007-04-20 22:00 ` Eric Botcazou
2007-04-28 16:25 ` Bernd Schmidt
2007-04-28 17:46 ` Eric Botcazou
2007-04-29 6:42 ` Bernd Schmidt
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=87tzp8twxh.fsf@firetop.home \
--to=rsandifo@nildram.co.uk \
--cc=aoliva@redhat.com \
--cc=bernds_cb1@t-online.de \
--cc=dberlin@dberlin.org \
--cc=dnovillo@acm.org \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=zippel@linux-m68k.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).