public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Paul Clarke <pc@us.ibm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, rs6000 2/2] Add compatible implementations of x86 SSSE3 intrinsics <tmmintrin.h>
Date: Tue, 23 Oct 2018 17:13:00 -0000	[thread overview]
Message-ID: <20181023162802.GN5205@gate.crashing.org> (raw)
In-Reply-To: <e489b02d-af5c-d373-5431-a371a91ef8de@us.ibm.com>

On Tue, Oct 23, 2018 at 10:29:35AM -0500, Paul Clarke wrote:
> On 10/22/2018 06:38 PM, Segher Boessenkool wrote:
> > On Mon, Oct 22, 2018 at 01:26:11PM -0500, Paul Clarke wrote:
> >> Target tests for the intrinsics defined in pmmintrin.h, copied from
> >> gcc.target/i386.
> >>
> >> Tested on POWER8 ppc64le and ppc64 (-m64 and -m32, the latter only reporting
> >> 16 new unsupported tests), and also by forcing -mcpu=power7 on ppc64.
> > 
> > Why are they unsupported?  lp64?  Why do many of those tests require
> > lp64 anyway?  It's not obvious to me.
> 
> None of the x86 intrinsics compatibility implementation code has thus far supported -m32, and I'd venture that it's not interesting to anyone.  Or at least not worth the effort.

You can use it with -m32 just fine.  Disabling the tests isn't a good idea.
Either disable the *feature*, or enable the tests.

> > You tested on a >=p8 (with a compiler defaulting to that, too) I hope ;-)
> 
> As stated, "Tested on POWER8 ppc64le" (which defaults to -mcpu=power8), or did you mean something else?

The big-endian part.  It does not default to p8 unless you arrange for
that specially.  The tests require p8 hardware, but that means if you
tested BE without --with-cpu=power8 or similar you really didn't test
anything.


Segher

      reply	other threads:[~2018-10-23 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22 20:09 Paul Clarke
2018-10-23  0:09 ` Segher Boessenkool
2018-10-23 16:28   ` Paul Clarke
2018-10-23 17:13     ` 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=20181023162802.GN5205@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=pc@us.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).