From: Segher Boessenkool <segher@kernel.crashing.org>
To: Carl Love <cel@us.ibm.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
"William J. Schmidt" <wschmidt@linux.vnet.ibm.com>
Subject: Re: [PATCH, rs6000] Fix AIX test case failures
Date: Wed, 18 Jul 2018 21:51:00 -0000 [thread overview]
Message-ID: <20180718215145.GX16221@gate.crashing.org> (raw)
In-Reply-To: <1531870798.5007.2.camel@us.ibm.com>
Hi Carl,
On Tue, Jul 17, 2018 at 04:39:58PM -0700, Carl Love wrote:
> I was requested to backport the patch for the AIX test case failures to
> GCC 8. The trunk patch applied cleanly to GCC 8. I updated the
> changelog patch, built and retested the patch on:
>
> Â Â Â powerpc64le-unknown-linux-gnu (Power 8 LE)Â Â
> Â Â Â Â powerpc64-unknown-linux-gnu (Power 8 BE)
> Â Â Â Â AIX 7200-00-01-1543 (Power 8 BE)
>
> With no regressions.
>
> Please let me know if it is OK to apply the patch to the GCC 8 branch.
Sure, it's okay. Thanks!
Segher
> 2018-07-17 Carl Love <cel@us.ibm.com>
>
> Backport from mainline
> 2018-07-16 Carl Love <cel@us.ibm.com>
>
> PR target/86414
> * gcc.target/powerpc/divkc3-2.c: Add dg-require-effective-target
> longdouble128.
> * gcc.target/powerpc/divkc3-3.c: Ditto.
> * gcc.target/powerpc/mulkc3-2.c: Ditto.
> * gcc.target/powerpc/mulkc3-3.c: Ditto.
> * gcc.target/powerpc/fold-vec-mergehl-double.c: Update counts.
> * gcc.target/powerpc/pr85456.c: Make check Linux and AIX specific.
prev parent reply other threads:[~2018-07-18 21:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 21:55 Carl Love
2018-06-25 9:44 ` Segher Boessenkool
2018-06-25 16:53 ` Carl Love
2018-06-25 17:04 ` Segher Boessenkool
2018-07-13 14:51 ` David Edelsohn
2018-07-13 21:00 ` Segher Boessenkool
2018-07-13 23:16 ` Carl Love
2018-07-14 3:08 ` David Edelsohn
2018-07-16 19:59 ` Segher Boessenkool
2018-07-17 23:40 ` Carl Love
2018-07-18 21:51 ` Segher Boessenkool [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=20180718215145.GX16221@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=cel@us.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=wschmidt@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).