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/103900] [12 Regression] ICE: in expand_expr_real_2, at expr.c:9771 with -O -fno-tree-dce -fno-tree-dse since r12-6173-g9ff206d3865df5cb
Date: Tue, 04 Jan 2022 10:03:31 +0000 [thread overview]
Message-ID: <bug-103900-4-IOnXWl8Nmk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103900-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103900
--- Comment #6 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Martin Liška from comment #5)
> No, it still crashes with the current master (g:fbb592407c9):
Ah, the compiler is blindly trying to generate V2QI XOR due to missing
one_cmplv2qi2 pattern. I have a patch that implements V2QI logic insns that
fixes the ICE.
next prev parent reply other threads:[~2022-01-04 10:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 8:07 [Bug rtl-optimization/103900] New: ICE: in expand_expr_real_2, at expr.c:9771 with -O -fno-tree-dce -fno-tree-dse zsojka at seznam dot cz
2022-01-04 8:39 ` [Bug rtl-optimization/103900] [12 Regression] ICE: in expand_expr_real_2, at expr.c:9771 with -O -fno-tree-dce -fno-tree-dse since r12-6173-g9ff206d3865df5cb marxin at gcc dot gnu.org
2022-01-04 9:41 ` [Bug target/103900] " ubizjak at gmail dot com
2022-01-04 9:47 ` pinskia at gcc dot gnu.org
2022-01-04 9:49 ` pinskia at gcc dot gnu.org
2022-01-04 9:49 ` marxin at gcc dot gnu.org
2022-01-04 10:03 ` ubizjak at gmail dot com [this message]
2022-01-04 10:04 ` ubizjak at gmail dot com
2022-01-04 18:44 ` cvs-commit at gcc dot gnu.org
2022-01-04 18:47 ` ubizjak at gmail dot com
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-103900-4-IOnXWl8Nmk@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).