public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Clarke <pc@us.ibm.com>
To: gcc-patches@gcc.gnu.org, Segher Boessenkool <segher@kernel.crashing.org>
Subject: [PATCH 0/3][rs6000] x86-compat vector intrinsics fixes for BE, 32bit
Date: Tue, 04 Dec 2018 14:58:00 -0000	[thread overview]
Message-ID: <24aa2417-0f4e-2f3b-6a20-27a4cb124c71@us.ibm.com> (raw)

Many of the tests for the x86-compatible vector intrinsics implementations
were protected by "#ifdef __BUILTIN_CPU_SUPPORTS__", which is only enabled
with recent enough glibc that in most environments, the test were silently
passing without actually testing anything.

Patches which follow:
01: Fix the implementations.
02: Fix the test cases.
03: Enable the tests to actually run the test code.

Bootstrap and regression tested on POWER8 ppc64le, ppc64(be), ppc(32bit be),
and POWER7 ppc64(be).

OK for trunk?

PC

             reply	other threads:[~2018-12-04 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 14:58 Paul Clarke [this message]
2018-12-04 18:07 ` Segher Boessenkool

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=24aa2417-0f4e-2f3b-6a20-27a4cb124c71@us.ibm.com \
    --to=pc@us.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=segher@kernel.crashing.org \
    /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).