From: Segher Boessenkool <segher@kernel.crashing.org>
To: Steven Munroe <munroesj@linux.vnet.ibm.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH, rs6000] Rev 2, 1/2 Add x86 MMX <mmintrin,h> intrinsics to GCC PPC64LE target
Date: Tue, 18 Jul 2017 22:29:00 -0000 [thread overview]
Message-ID: <20170718222919.GS13471@gate.crashing.org> (raw)
In-Reply-To: <1500318900.22326.16.camel@oc7878010663>
Hi!
On Mon, Jul 17, 2017 at 02:15:00PM -0500, Steven Munroe wrote:
> Correct the problems Segher found in review and added a changes to deal
> with the fallout from the __builtin_cpu_supports warning for older
> distros.
>
> Tested on P8 LE and P6/P7/P8 BE. No new tests failures.
>
> ./gcc/ChangeLog:
>
> 2017-07-17 Steven Munroe <munroesj@gcc.gnu.org>
>
> * config.gcc (powerpc*-*-*): Add mmintrin.h.
> * config/rs6000/mmintrin.h: New file.
> * config/rs6000/x86intrin.h [__ALTIVEC__]: Include mmintrin.h.
Okay for trunk. Thanks,
Segher
prev parent reply other threads:[~2017-07-18 22:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 19:16 Steven Munroe
2017-07-18 22:29 ` 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=20170718222919.GS13471@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=munroesj@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).