From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "Kewen.Lin" <linkw@linux.vnet.ibm.com>,
gcc-patches@gcc.gnu.org,
Bill Schmidt <wschmidt@linux.ibm.com>
Subject: Re: [PATCH] rs6000: Add missing prototypes for vec_ld/vec_st
Date: Sat, 19 Jan 2019 01:05:00 -0000 [thread overview]
Message-ID: <20190119010425.GX14180@gate.crashing.org> (raw)
In-Reply-To: <20190118221512.GU30353@tucnak>
On Fri, Jan 18, 2019 at 11:15:12PM +0100, Jakub Jelinek wrote:
> On Wed, Jan 16, 2019 at 10:08:46PM +0800, Kewen.Lin wrote:
> > * gcc.target/powerpc/altivec_vld_vst_addr.c: New test.
>
> This test fails on powerpc64-linux, both with -m32 and -m64:
I missed that. Thanks Jakub.
Kewen, please split the "vector long long" tests to a separate testcase,
and use -mvsx and powerpc_vsx_ok there (instead of -maltivec and
powerpc_altivec_ok).
Segher
next prev parent reply other threads:[~2019-01-19 1:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 14:09 Kewen.Lin
2019-01-16 17:08 ` Segher Boessenkool
2019-01-18 22:15 ` Jakub Jelinek
2019-01-19 1:05 ` Segher Boessenkool [this message]
2019-01-19 13:27 ` [PATCH v2] " Kewen.Lin
2019-01-19 22:23 ` 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=20190119010425.GX14180@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=linkw@linux.vnet.ibm.com \
--cc=wschmidt@linux.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).