From: Artem Shinkarov <artyom.shinkaroff@gmail.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Mike Stump <mikestump@comcast.net>,
"H.J. Lu" <hjl.tools@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: New warning for expanded vector operations
Date: Fri, 14 Oct 2011 14:02:00 -0000 [thread overview]
Message-ID: <CABYV9SUSzwW10qrQ-UuFJCjmOf55ePZ-nRSNbFEm5qr9CZh6Sg@mail.gmail.com> (raw)
In-Reply-To: <CABYV9SXMnKbmPQjk2yMZCy4wqh96NdxMKo4DrjpanF-o2Titew@mail.gmail.com>
On Thu, Oct 13, 2011 at 10:40 AM, Artem Shinkarov
<artyom.shinkaroff@gmail.com> wrote:
> On Thu, Oct 13, 2011 at 10:23 AM, Richard Guenther
> <richard.guenther@gmail.com> wrote:
>> On Thu, Oct 13, 2011 at 10:59 AM, Mike Stump <mikestump@comcast.net> wrote:
>>> On Oct 12, 2011, at 2:37 PM, Artem Shinkarov wrote:
>>>> This patch fixed PR50704.
>>>>
>>>> gcc/testsuite:
>>>> * gcc.target/i386/warn-vect-op-3.c: Exclude ia32 target.
>>>> * gcc.target/i386/warn-vect-op-1.c: Ditto.
>>>> * gcc.target/i386/warn-vect-op-2.c: Ditto.
>>>>
>>>> Ok for trunk?
>>>
>>> Ok. Is this x32 clean? :-) If not, HJ will offer an even better spelling.
>>
>> I suppose you instead want sth like
>>
>> { dg-require-effective-target lp64 }
>>
>> ?
>>
>
> See our discussion with HJ here:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50704
> /* { dg-do compile { target { ! { ia32 } } } } */ was his idea. As
> far as x32 sets UNITS_PER_WORD to 8, these tests should work fine.
>
> Artem.
>
Ping.
So can I commit the changes?
Thanks,
Artem.
next prev parent reply other threads:[~2011-10-14 13:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 22:25 Artem Shinkarov
2011-10-05 8:40 ` Richard Guenther
2011-10-05 11:31 ` Artem Shinkarov
2011-10-05 11:37 ` Richard Guenther
2011-10-07 7:13 ` Artem Shinkarov
2011-10-07 8:01 ` Artem Shinkarov
2011-10-10 11:15 ` Richard Guenther
2011-10-10 13:27 ` Artem Shinkarov
2011-10-11 11:40 ` Richard Guenther
2011-10-11 17:26 ` Artem Shinkarov
2011-10-12 16:25 ` H.J. Lu
2011-10-12 22:10 ` Artem Shinkarov
2011-10-13 9:32 ` Mike Stump
2011-10-13 10:17 ` Richard Guenther
2011-10-13 10:18 ` Artem Shinkarov
2011-10-14 14:02 ` Artem Shinkarov [this message]
2011-10-14 14:15 ` Richard Guenther
2011-10-14 16:05 ` Artem Shinkarov
2011-10-14 18:31 ` Mike Stump
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=CABYV9SUSzwW10qrQ-UuFJCjmOf55ePZ-nRSNbFEm5qr9CZh6Sg@mail.gmail.com \
--to=artyom.shinkaroff@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=mikestump@comcast.net \
--cc=richard.guenther@gmail.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).