public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Martin Liska <mliska@suse.cz>
Subject: Re: [PATCH] Fix for PR ipa/64503
Date: Thu, 08 Jan 2015 18:42:00 -0000	[thread overview]
Message-ID: <CAFULd4a8NNYc5HLM=bkiyGe0w24G=juanD8L3nC+S1h5zsUY_Q@mail.gmail.com> (raw)
In-Reply-To: <20150108170435.GH1405@tucnak.redhat.com>

On Thu, Jan 8, 2015 at 6:04 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> On Wed, Jan 07, 2015 at 01:43:59PM +0100, Uros Bizjak wrote:
>> Hello!
>>
>> >>>> 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.
>> >
>> > Thanks for testing. May I take this as approval of the patch.
>> > I don't know, if you have a permission to accept my patch ;)
>>
>> Unfortunately, I have no approval power here. Luckilly, I know someone
>> who has ;)
>
> I don't know how portable scalbnl actually is in reality, so it would be
> nice to hear from port maintainers whether say newlib, android, darwin,
> cygwin, aix etc. have it.

Newlib has it.

Other than that:

       exp2(), exp2f(), exp2l():
           _XOPEN_SOURCE >= 600 || _ISOC99_SOURCE || _POSIX_C_SOURCE >= 200112L;
           or cc -std=c99

       scalbln(), scalblnf(), scalblnl():
              _XOPEN_SOURCE >= 600 || _ISOC99_SOURCE ||
_POSIX_C_SOURCE >= 200112L;
              or cc -std=c99

Since we are replacing exp2 with scalbln, we have the same
requirements as before, at least we won't regress here.

Uros.

  reply	other threads:[~2015-01-08 18:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 12:44 Uros Bizjak
2015-01-08 17:04 ` Jakub Jelinek
2015-01-08 18:42   ` Uros Bizjak [this message]
2015-01-08 19:05     ` Jakub Jelinek
2015-01-08 19:34   ` Mike Stump
  -- strict thread matches above, loose matches on Subject: below --
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

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='CAFULd4a8NNYc5HLM=bkiyGe0w24G=juanD8L3nC+S1h5zsUY_Q@mail.gmail.com' \
    --to=ubizjak@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=mliska@suse.cz \
    /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).