public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104445] [12 Regression] ICE in vect_create_partial_epilog, at tree-vect-loop.cc:5098
Date: Wed, 09 Feb 2022 11:33:09 +0000 [thread overview]
Message-ID: <bug-104445-4-kJWQrQoiG2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104445-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104445
--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Uroš Bizjak from comment #9)
> (In reply to rguenther@suse.de from comment #8)
> > > (In reply to Richard Biener from comment #6)
> > > > We are missing vec_extractv2sisi or vec_extractv8qiv4qi, with -mno-mmx -mavx.
> > > > It seems we have addv2si3 available though.
> > >
> > > vec_extractv2sisi is available in mmx.md even with -mno-mmx:
> > >
> > > (define_expand "vec_extractv2sisi"
> > > [(match_operand:SI 0 "register_operand")
> > > (match_operand:V2SI 1 "register_operand")
> > > (match_operand 2 "const_int_operand")]
> > > "TARGET_MMX || TARGET_MMX_WITH_SSE"
> > > {
> > > ix86_expand_vector_extract (TARGET_MMX_WITH_SSE, operands[0],
> > > operands[1], INTVAL (operands[2]));
> > > DONE;
> > > })
> >
> > But I think with -m32 we have !TARGET_MMX_WITH_SSE
>
> Yes, that is true. Please note that in this case, we don't have addv2si3 as
> well as it also depends on TARGET_MMX_WITH_SSE.
Oh, the testcase doesn't use add but xorv8qi3. But since we're using
DImode for v8qi we of course do have support for it but also obviously
later will fail the vec_extract obtab queries ... a disi vec_extract
does not exist.
So it's the vectorizers fault to not properly account for scalar integer mode
vector types.
next prev parent reply other threads:[~2022-02-09 11:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 19:39 [Bug c/104445] New: " gscfq@t-online.de
2022-02-08 20:48 ` [Bug tree-optimization/104445] " pinskia at gcc dot gnu.org
2022-02-09 5:45 ` pinskia at gcc dot gnu.org
2022-02-09 5:48 ` pinskia at gcc dot gnu.org
2022-02-09 7:31 ` rguenth at gcc dot gnu.org
2022-02-09 9:55 ` rguenth at gcc dot gnu.org
2022-02-09 10:01 ` ubizjak at gmail dot com
2022-02-09 10:21 ` rguenth at gcc dot gnu.org
2022-02-09 10:26 ` ubizjak at gmail dot com
2022-02-09 10:48 ` rguenther at suse dot de
2022-02-09 10:59 ` ubizjak at gmail dot com
2022-02-09 11:33 ` rguenth at gcc dot gnu.org [this message]
2022-02-09 13:03 ` cvs-commit at gcc dot gnu.org
2022-02-09 13:03 ` 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-104445-4-kJWQrQoiG2@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).