From: Richard Biener <richard.guenther@gmail.com>
To: "Maciej W. Rozycki" <macro@embecosm.com>
Cc: "haochen.jiang" <haochenj@ecsmtp.sh.intel.com>,
gcc-regression@gcc.gnu.org, gcc-patches@gcc.gnu.org,
haochen.jiang@intel.com
Subject: Re: [r14-2639 Regression] FAIL: gcc.dg/vect/bb-slp-pr95839-v8.c scan-tree-dump slp2 "optimized: basic block" on Linux/x86_64
Date: Thu, 20 Jul 2023 15:27:34 +0200 [thread overview]
Message-ID: <CAFiYyc36k2qf3p5iOsxFAAfdf0zJiV3bej_iv6Lfj_pxOugNjA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.2307201406060.28892@tpp.orcam.me.uk>
On Thu, Jul 20, 2023 at 3:13 PM Maciej W. Rozycki <macro@embecosm.com> wrote:
>
> On Thu, 20 Jul 2023, Richard Biener wrote:
>
> > > c1e420549f2305efb70ed37e693d380724eb7540 is the first bad commit
> > > commit c1e420549f2305efb70ed37e693d380724eb7540
> > > Author: Maciej W. Rozycki <macro@embecosm.com>
> > > Date: Wed Jul 19 11:59:29 2023 +0100
> > >
> > > testsuite: Add 64-bit vector variant for bb-slp-pr95839.c
> >
> > I think the issue is we disable V2SF on ia32 because of the conflict
> > with MMX which we
> > don't want to use.
>
> I'm not sure if I have a way to test with such a target. Would you
> expect:
>
> /* { dg-require-effective-target vect64 } */
>
> to cover it? If so, then I'll put it back as in the original version and
> post for Haochen to verify.
Yeah, that should work here.
Richard.
> Maciej
next prev parent reply other threads:[~2023-07-20 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 11:44 haochen.jiang
2023-07-20 12:51 ` Richard Biener
2023-07-20 13:13 ` Maciej W. Rozycki
2023-07-20 13:27 ` Richard Biener [this message]
2023-07-21 1:51 ` Jiang, Haochen
2023-07-22 16:57 ` [committed] testsuite: Limit bb-slp-pr95839-v8.c to 64-bit vector targets Maciej W. Rozycki
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=CAFiYyc36k2qf3p5iOsxFAAfdf0zJiV3bej_iv6Lfj_pxOugNjA@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-regression@gcc.gnu.org \
--cc=haochen.jiang@intel.com \
--cc=haochenj@ecsmtp.sh.intel.com \
--cc=macro@embecosm.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).