public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@vnet.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	       Tulio Magno Quites Machado Filho
	<tuliom@linux.vnet.ibm.com>,
	       Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH, rs6000] Modify libgcc's float128 IFUNC resolver functions to use __builtin_cpu_supports()
Date: Thu, 20 Jul 2017 14:52:00 -0000	[thread overview]
Message-ID: <58a12625-d9f0-5559-6269-e3ff578ef91e@vnet.ibm.com> (raw)
In-Reply-To: <72edf0f6-6ada-1780-7909-506efa0402bd@vnet.ibm.com>

On 7/10/17 2:52 PM, Peter Bergner wrote:
> On 7/10/17 9:48 AM, Segher Boessenkool wrote:
>> On Fri, Jul 07, 2017 at 07:14:25PM -0500, Peter Bergner wrote:
>>> On 7/7/17 4:13 PM, Peter Bergner wrote:
>>>> On 7/7/17 10:18 AM, Segher Boessenkool wrote:
>>>>> On Thu, Jul 06, 2017 at 04:21:48PM -0500, Peter Bergner wrote:
>>>>>> 	* config/rs6000/float128-ifunc.c: Don't include auxv.h.
>>>>>> 	(have_ieee_hw_p): Delete function.
>>>>>> 	(SW_OR_HW) Use __builtin_cpu_supports().
>>>>>
>>>>> Okay for trunk.  Thanks!
>>>>
>>>> Given Florian wants this in now to fix a Fedora blocker, I have
>>>> committed this to trunk.  We need the fix on GCC 6 and GCC 5 as
>>>> well, so ok there assuming bootstrapping / regtesting are clean?
>>>
>>> FYI, the bootstrap and regtesting were clean on both the GCC 7 and
>>> GCC 6 release branches.  Ok for those branches?
>>
>> Okay for 7 and 6.  If it is a blocker (or you have another reason you
>> cannot wait to see if regressions pop up), please make sure you test it
>> on many different systems.
> 
> The backports bootstrapped and regtested with no regressions on
> powerpc64le-linux and powerpc64-linux, while running the testsuite
> in both 32-bit and 64-bit modes.
> 
> I am heading off to Paris on vacation later today, and will return on
> the 19th.  I will commit this when I return.

Backports to GCC 7 and GCC 6 release branches have now been committed.

Peter

      reply	other threads:[~2017-07-20 14:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 21:22 Peter Bergner
2017-07-07 10:12 ` Florian Weimer
2017-07-07 15:19 ` Segher Boessenkool
2017-07-07 21:13   ` Peter Bergner
2017-07-08  0:14     ` Peter Bergner
2017-07-10 14:49       ` Segher Boessenkool
2017-07-10 19:52         ` Peter Bergner
2017-07-20 14:52           ` Peter Bergner [this message]

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=58a12625-d9f0-5559-6269-e3ff578ef91e@vnet.ibm.com \
    --to=bergner@vnet.ibm.com \
    --cc=fweimer@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=segher@kernel.crashing.org \
    --cc=tuliom@linux.vnet.ibm.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).