public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96744] [11 Regression] FAIL: gcc.target/i386/avx512bitalgvl-vpopcntb-1.c execution test
Date: Thu, 27 Aug 2020 11:09:21 +0000 [thread overview]
Message-ID: <bug-96744-4-eETQfwPCVq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96744-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96744
--- Comment #11 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Hongtao.liu from comment #9)
> > > However, the patch assumes that avx512vp2intersect implies mavx512dq,
> >
> > Let me check this part.
>
> Confirmed, avx512vp2intersect implies avx512dq.
>
> Should bellow in the same patch with attachment 49114 [details], or a
> separate patch?
Please commit this patch first (the patch is pre-approved), followed by
attachment 49119 (which is also pre-approved as a separate patch) after they
pass standard bootstrap/regression test cycle.
next prev parent reply other threads:[~2020-08-27 11:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 12:28 [Bug target/96744] New: " hjl.tools at gmail dot com
2020-08-23 15:40 ` [Bug target/96744] " cvs-commit at gcc dot gnu.org
2020-08-24 7:47 ` crazylht at gmail dot com
2020-08-24 12:05 ` ubizjak at gmail dot com
2020-08-24 14:08 ` ubizjak at gmail dot com
2020-08-24 14:11 ` ubizjak at gmail dot com
2020-08-24 14:14 ` ubizjak at gmail dot com
2020-08-25 5:14 ` crazylht at gmail dot com
2020-08-25 11:38 ` rguenth at gcc dot gnu.org
2020-08-27 8:52 ` crazylht at gmail dot com
2020-08-27 9:09 ` crazylht at gmail dot com
2020-08-27 11:09 ` ubizjak at gmail dot com [this message]
2020-08-28 7:47 ` cvs-commit at gcc dot gnu.org
2020-08-28 7:53 ` cvs-commit at gcc dot gnu.org
2020-09-15 10:23 ` cvs-commit at gcc dot gnu.org
2020-09-15 10:24 ` crazylht at gmail dot com
2020-10-12 12:28 ` rguenth at gcc dot gnu.org
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=bug-96744-4-eETQfwPCVq@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).