public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103463] [12 Regression] ICE: in ix86_attr_length_immediate_default, at config/i386/i386.c:16686 with -Os -fno-tree-dominator-opts -fno-tree-vrp
Date: Tue, 30 Nov 2021 07:58:06 +0000 [thread overview]
Message-ID: <bug-103463-4-2iaujVOsPm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103463-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103463
--- Comment #4 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Hongtao.liu from comment #3)
> (In reply to Hongtao.liu from comment #1)
> > It should be fixed by
> > https://gcc.gnu.org/pipermail/gcc-patches/2021-November/585613.html
>
> Hmm, it looks to be broken again.
I thought is was same problem as
https://gcc.gnu.org/pipermail/gcc-regression/2021-November/075893.html, but
it's not.
It's caused by r12-5558
the insn hit gcc_assert in ix86_attr_length_immediate_default is
(insn 20 19 21 2 (parallel [
(set (reg:DI 1 dx [orig:110 bar0_u128_0 ] [110])
(ior:DI (lshiftrt:DI (reg:DI 1 dx [orig:110 bar0_u128_0 ]
[110])
(const_int 0 [0]))
(subreg:DI (ashift:TI (zero_extend:TI (reg:DI 0 ax
[orig:111+8 ] [111]))
(const_int 64 [0x40])) 0)))
(clobber (reg:CC 17 flags))
which set len = 1 and hit gcc_assert (!len);
if (IN_RANGE (ival, -128, 127))
{
len = 1;
continue;
}
}
next prev parent reply other threads:[~2021-11-30 7:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 7:22 [Bug target/103463] New: " zsojka at seznam dot cz
2021-11-29 7:37 ` [Bug target/103463] " pinskia at gcc dot gnu.org
2021-11-29 7:43 ` crazylht at gmail dot com
2021-11-29 8:58 ` marxin at gcc dot gnu.org
2021-11-29 9:46 ` cvs-commit at gcc dot gnu.org
2021-11-30 7:44 ` crazylht at gmail dot com
2021-11-30 7:58 ` crazylht at gmail dot com [this message]
2021-11-30 8:19 ` crazylht at gmail dot com
2021-11-30 23:39 ` cvs-commit at gcc dot gnu.org
2021-12-01 0:51 ` crazylht at gmail dot com
2021-12-03 10:14 ` pinskia at gcc dot gnu.org
2021-12-04 21:44 ` pinskia 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-103463-4-2iaujVOsPm@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).