From: Jeff Law <law@redhat.com>
To: "Uros Bizjak" <ubizjak@gmail.com>, "Martin Liška" <mliska@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
"hubicka >> Jan Hubicka" <hubicka@ucw.cz>
Subject: Re: [PATCH] Fix for PR ipa/64503
Date: Fri, 09 Jan 2015 05:18:00 -0000 [thread overview]
Message-ID: <54AF64A0.1050605@redhat.com> (raw)
In-Reply-To: <CAFULd4Y4AOryVVG_aQERyF7=BwYHb6SYXUrRW_7Ou1saTLh5Og@mail.gmail.com>
On 01/07/15 03:55, Uros Bizjak wrote:
> On Tue, Jan 6, 2015 at 7:25 PM, Uros Bizjak <ubizjak@gmail.com> wrote:
>
>>> There's suggested patch for PR ipa/64503 that was tested on x86_64 and it
>>> works.
>>> I would like to ask Uros to test it on an aplha machine before we install
>>> the patch.
>>
>> Yes, this works for me on all IPA tests that were failing previously [1].
>>
>> I am restarting the bootstrap + regtest, it will take ~10 hours, but I
>> don't expect any surprises there.
>
> The patch was bootstrapped and regression tested on
> alphaev68-linux-gnu [2] and everything was OK.
>
> [2] https://gcc.gnu.org/ml/gcc-testresults/2015-01/msg00577.html
I'll approve the patch. scalbln is part of the ISO C standard as well
as IEEE 1003.1, so I think we can rely on it. If there's a host
without, then we'll have to figure something out if/when the issue is
reported.
jeff
next prev parent reply other threads:[~2015-01-09 5:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 17:49 Martin Liška
2015-01-06 18:25 ` Uros Bizjak
2015-01-07 10:55 ` Uros Bizjak
2015-01-07 11:35 ` Martin Liška
2015-01-09 5:18 ` Jeff Law [this message]
2015-01-07 12:44 Uros Bizjak
2015-01-08 17:04 ` Jakub Jelinek
2015-01-08 18:42 ` Uros Bizjak
2015-01-08 19:05 ` Jakub Jelinek
2015-01-08 19:34 ` Mike Stump
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=54AF64A0.1050605@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=mliska@suse.cz \
--cc=ubizjak@gmail.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).