From: "H.J. Lu" <hjl.tools@gmail.com>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: Jeff Law <law@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: New optimization for reload_combine
Date: Sat, 17 Jul 2010 17:27:00 -0000 [thread overview]
Message-ID: <AANLkTimJulqzuUyV-vfDoyxAYm-xxfgXHragLz0zJpN8@mail.gmail.com> (raw)
In-Reply-To: <4C41E5A0.3050907@codesourcery.com>
On Sat, Jul 17, 2010 at 10:17 AM, Bernd Schmidt <bernds@codesourcery.com> wrote:
> On 07/17/2010 06:14 PM, H.J. Lu wrote:
>> On Sat, Jul 17, 2010 at 8:59 AM, Bernd Schmidt <bernds@codesourcery.com> wrote:
>>> On 07/17/2010 05:03 PM, H.J. Lu wrote:
>>>> It is more than that. It failed to boostrap on Linux/ia32 when
>>>> configured with
>>>>
>>>> --enable-clocale=gnu --with-system-zlib --enable-shared
>>>> --with-demangler-in-ld --with-fpmath=sse
>>>
>>> I can't seem to reproduce this. Is that the full command line?
>>>
>>>
>>
>> I used:
>>
>> ../src-trunk/configure \
>> --enable-clocale=gnu --with-system-zlib --enable-shared --with-
>> demangler-in-ld -with-plugin-ld=ld.gold --enable-gold --with-fpmath=sse
>>
>> on Fedora 12/ia32.
>
> I'm on Gentoo, without gold - not sure whether that made a difference,
Is that possible for you to install Fedora 12/13? 64bit Fedora is fine.
You can bootstrap 32bit gcc on 64bit Fedora.
> but I'm not seeing these failures. I don't have access to SPEC2k6
> either. Can you isolate any testcases?
>
SPEC CPU 2006 failure is the run-time comparison failure.
It won't be easy to find a small testcase. Gcc bootstrap comparison
failure and testsuite regressions are much easier to debug.
Thanks.
--
H.J.
next prev parent reply other threads:[~2010-07-17 17:27 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 10:35 Bernd Schmidt
2010-07-16 18:32 ` Jeff Law
2010-07-16 23:50 ` Bernd Schmidt
2010-07-17 2:38 ` H.J. Lu
2010-07-17 14:25 ` Bernd Schmidt
2010-07-17 15:03 ` H.J. Lu
2010-07-17 15:10 ` IainS
2010-07-17 16:00 ` Bernd Schmidt
2010-07-17 16:15 ` H.J. Lu
2010-07-17 17:18 ` Bernd Schmidt
2010-07-17 17:27 ` H.J. Lu [this message]
2010-07-17 17:29 ` IainS
2010-07-18 18:15 ` H.J. Lu
2010-07-19 10:01 ` Bernd Schmidt
2010-07-19 13:27 ` H.J. Lu
2010-07-20 11:46 ` Bernd Schmidt
2010-07-20 15:33 ` Jeff Law
2010-07-20 15:34 ` Bernd Schmidt
2010-07-20 15:40 ` Jakub Jelinek
2010-07-19 15:41 ` x86_64 varargs setup jump table Richard Henderson
2010-07-19 15:56 ` H.J. Lu
2010-07-19 20:57 ` H.J. Lu
2010-07-19 21:14 ` Richard Henderson
2010-07-20 16:32 ` Richard Henderson
2010-07-20 23:05 ` Richard Henderson
2010-07-20 23:21 ` Sebastian Pop
2010-07-22 13:52 ` H.J. Lu
2010-07-22 18:03 ` Sebastian Pop
2010-07-22 18:15 ` Richard Henderson
2010-07-22 18:17 ` Richard Henderson
2010-07-22 18:20 ` Sebastian Pop
2010-07-21 23:15 ` H.J. Lu
2010-07-22 21:53 ` Fix target/45027 [was: x86_64 varargs setup jump table] Richard Henderson
2010-07-23 9:07 ` Richard Guenther
2010-07-19 16:09 ` x86_64 varargs setup jump table Andi Kleen
2010-07-19 16:16 ` H.J. Lu
2010-07-19 16:26 ` Andi Kleen
2010-07-19 16:23 ` Jan Hubicka
2010-07-19 16:19 ` New optimization for reload_combine Jeff Law
2010-11-04 4:30 ` H.J. Lu
2010-07-16 19:45 ` Paolo Bonzini
2010-07-16 19:55 ` Bernd Schmidt
2010-07-16 20:24 ` Paolo Bonzini
2010-07-19 16:11 ` Mark Mitchell
2010-07-19 16:13 ` Jeff Law
2010-07-19 16:31 ` Paolo Bonzini
2010-07-26 10:13 ` IainS
2010-07-26 10:46 ` Bernd Schmidt
2010-07-27 0:53 ` 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=AANLkTimJulqzuUyV-vfDoyxAYm-xxfgXHragLz0zJpN8@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.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).