public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rdapp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/112406] [14 Regression] Several SPECCPU 2017 benchmarks fail with on internal compiler error: in expand_insn, at optabs.cc:8305 after g:01c18f58d37865d5f3bbe93e666183b54ec608c7
Date: Wed, 08 Nov 2023 11:06:46 +0000 [thread overview]
Message-ID: <bug-112406-4-W4iqvtcXpS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112406-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112406
--- Comment #8 from Robin Dapp <rdapp at gcc dot gnu.org> ---
Ah of course it's not the first argument but the mask. During vectorization we
already create
fail1.c:15:10: note: add new stmt: vect__ifc__141.81_358 = .COND_ADD
(vect_cst__356, vect_GetImageChannelMoments_M00_0_lsm.74_338, vect_cst__357,
vect_GetImageChannelMoments_M00_0_lsm.74_338);
where vect_cst__356 is
vector([16,16]) unsigned char vect_cst__356;
fail1.c:15:10: note: created new init_stmt: _355 = (unsigned char) _114;
fail1.c:15:10: note: created new init_stmt: vect_cst__356 =
[vec_duplicate_expr] _355;
The type comes from vect_get_vec_defs_for_operand.
next prev parent reply other threads:[~2023-11-08 11:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 11:20 [Bug middle-end/112406] New: [14 Regression] Several SPECCPU 2017 benchmarks fail with internal compiler error: in expand_insn, at optabs.cc:8305 tnfchris at gcc dot gnu.org
2023-11-06 13:11 ` [Bug middle-end/112406] [14 Regression] Several SPECCPU 2017 benchmarks fail with LTO on " rguenth at gcc dot gnu.org
2023-11-07 11:23 ` tnfchris at gcc dot gnu.org
2023-11-07 21:38 ` cvs-commit at gcc dot gnu.org
2023-11-08 7:00 ` rguenth at gcc dot gnu.org
2023-11-08 7:02 ` tnfchris at gcc dot gnu.org
2023-11-08 10:24 ` tnfchris at gcc dot gnu.org
2023-11-08 10:25 ` [Bug middle-end/112406] [14 Regression] Several SPECCPU 2017 benchmarks fail with on internal compiler error: in expand_insn, at optabs.cc:8305 after g:01c18f58d37865d5f3bbe93e666183b54ec608c7 tnfchris at gcc dot gnu.org
2023-11-08 10:40 ` rdapp at gcc dot gnu.org
2023-11-08 11:06 ` rdapp at gcc dot gnu.org [this message]
2023-11-08 11:24 ` rdapp at gcc dot gnu.org
2023-11-08 15:50 ` tnfchris at gcc dot gnu.org
2023-11-08 15:54 ` rdapp at gcc dot gnu.org
2023-11-17 20:35 ` cvs-commit at gcc dot gnu.org
2023-11-20 9:23 ` cvs-commit at gcc dot gnu.org
2023-11-21 4:45 ` tnfchris at gcc dot gnu.org
2023-11-21 7:38 ` rdapp at gcc dot gnu.org
2023-11-21 9:07 ` tnfchris at gcc dot gnu.org
2023-11-21 9:33 ` rdapp at gcc dot gnu.org
2023-11-21 10:29 ` rdapp at gcc dot gnu.org
2023-11-21 10:51 ` tnfchris at gcc dot gnu.org
2023-11-21 11:22 ` rdapp at gcc dot gnu.org
2023-11-21 11:40 ` rdapp at gcc dot gnu.org
2023-11-21 20:11 ` cvs-commit at gcc dot gnu.org
2023-11-23 12:08 ` tnfchris at gcc dot gnu.org
2023-12-02 19:20 ` pinskia at gcc dot gnu.org
2023-12-03 19:04 ` cvs-commit 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-112406-4-W4iqvtcXpS@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).