public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: Hongtao Liu <crazylht@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH]Several intrinsic macros lack a closing parenthesis[PR93274]
Date: Fri, 14 Feb 2020 07:06:00 -0000	[thread overview]
Message-ID: <CAFULd4Zzf-6W8OeMxESKsDd0SxfGnrmQr0oDU0htZ5bLpbSo4w@mail.gmail.com> (raw)
In-Reply-To: <CAMZc-byOVNCZitUS7T=W_rOKZm9RO2VpuPmyeE-26myPvTGh5A@mail.gmail.com>

On Fri, Feb 14, 2020 at 7:03 AM Hongtao Liu <crazylht@gmail.com> wrote:
>
> On Thu, Feb 13, 2020 at 5:31 PM Hongtao Liu <crazylht@gmail.com> wrote:
> >
> > On Thu, Feb 13, 2020 at 5:12 PM Uros Bizjak <ubizjak@gmail.com> wrote:
> > >
> > > On Thu, Feb 13, 2020 at 9:53 AM Jakub Jelinek <jakub@redhat.com> wrote:
> > > >
> > > > On Thu, Feb 13, 2020 at 09:39:05AM +0100, Uros Bizjak wrote:
> > > > > > Changelog
> > > > > > gcc/
> > > > > >        * config/i386/avx512vbmi2intrin.h
> > > > > >        (_mm512_[,mask_,maskz_]shrdi_epi16,
> > > > > >        _mm512_[,mask_,maskz_]shrdi_epi32,
> > > > > >        _m512_[,mask_,maskz_]shrdi_epi64,
> > > > > >        _mm512_[,mask_,maskz_]shldi_epi16,
> > > > > >        _mm512_[,mask_,maskz_]shldi_epi32,
> > > > > >        _m512_[,mask_,maskz_]shldi_epi64): Fix typo of lacking a
> > > > > >        closing parenthesis.
> > > > > >        * config/i386/avx512vbmi2vlintrin.h
> > > > > >        (_mm256_[,mask_,maskz_]shrdi_epi16,
> > > > > >        _mm256_[,mask_,maskz_]shrdi_epi32,
> > > > > >        _m256_[,mask_,maskz_]shrdi_epi64,
> > > > > >        _mm_[,mask_,maskz_]shrdi_epi16,
> > > > > >        _mm_[,mask_,maskz_]shrdi_epi32,
> > > > > >        _mm_[,mask_,maskz_]shrdi_epi64,
> > > > > >        _mm256_[,mask_,maskz_]shldi_epi16,
> > > > > >        _mm256_[,mask_,maskz_]shldi_epi32,
> > > > > >        _m256_[,mask_,maskz_]shldi_epi64,
> > > > > >        _mm_[,mask_,maskz_]shldi_epi16,
> > > > > >        _mm_[,mask_,maskz_]shldi_epi32,
> > > > > >        _mm_[,mask_,maskz_]shldi_epi64): Ditto.
> > > > > >
> > > > > > gcc/testsuite/
> > > > > >        * gcc.target/i386/avx512vbmi2-vpshld-1.c: New test.
> > > > > >        * gcc.target/i386/avx512vbmi2-vpshld-O0-1.c: Ditto.
> > > > > >        * gcc.target/i386/avx512vbmi2-vpshrd-1.c: Ditto.
> > > > > >        * gcc.target/i386/avx512vbmi2-vpshrd-O0-1.c: Ditto.
> > > > > >        * gcc.target/i386/avx512vl-vpshld-O0-1.c: Ditto.
> > > > > >        * gcc.target/i386/avx512vl-vpshrd-O0-1.c: Ditto.
> > > > >
> > > > > This is obvious patch, so OK for mainline and backports.
> > > >
> > > > The header changes sure, but for the testsuite, the standard way
> > > > would be to have it covered in the standard tests we have for this.
> > > > I think that is gcc.target/i386/sse-{13,14,22a,23}.c, so it would be worth
> > > > trying to figure out why it hasn't caught that.
> > >
> > > Indeed. It looks that these macros are not listed in sse-14.c, which
> > > would catch the problem. So, there is no need for new -O0 tests,
> > > please add missing functions to sse-14.c and sse-22.c testcases. I was
> > > also surprised that no testsuite coverage for vbmi2 functions was
> > > added at submission.
> > >
> > Yes, i saw that, thanks.
> > > Uros.
> > >
> > > > And, I don't think we allow any wildcards etc. (and [,whatever,whateverelse]
> > > > isn't even one, neither regexp nor shell wildcard) in the names of functions
> > > > changed, they can appear in the description text, but for the names of
> > > > macros one needs to list them all expanded, people do grep for those.
> > > >
> > > >         Jakub
> > > >
> >
> >
> >
> > --
> > BR,
> > Hongtao
>
> Update patch:
> Update Changelog, delete O0 testcase, and add testcase in sse-14.c, sse-22.c

OK.

Thanks,
Uros.

> --
> BR,
> Hongtao

  reply	other threads:[~2020-02-14  7:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13  8:39 Uros Bizjak
2020-02-13  8:53 ` Jakub Jelinek
2020-02-13  9:12   ` Uros Bizjak
2020-02-13  9:31     ` Hongtao Liu
2020-02-14  6:03       ` Hongtao Liu
2020-02-14  7:06         ` Uros Bizjak [this message]
2020-02-14 11:16           ` Uros Bizjak
2020-02-14 13:19             ` Hongtao Liu
2020-02-18  8:25 ` Uros Bizjak
2020-02-18 11:01   ` Hongtao Liu
2020-02-19  2:31     ` Hongtao Liu
  -- strict thread matches above, loose matches on Subject: below --
2020-02-13  3:54 Hongtao Liu

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=CAFULd4Zzf-6W8OeMxESKsDd0SxfGnrmQr0oDU0htZ5bLpbSo4w@mail.gmail.com \
    --to=ubizjak@gmail.com \
    --cc=crazylht@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).