public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jcmvbkbc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107645] internal compiler error: RTL check: expected elt 0 type 'e' or 'u', have 'E' (rtx unspec) in symbolic_operand_1, at config/m68k/predicates.md:144 Date: Fri, 11 Nov 2022 18:54:36 +0000 [thread overview] Message-ID: <bug-107645-4-BYcYGFTs7Q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107645-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107645 --- Comment #1 from jcmvbkbc at gcc dot gnu.org --- ICE in the reproducer is generated when predicate 'symbolic_operand' is applied to the 'const' node in the following rtl: (insn 342 341 343 35 (set (reg:SI 97) (mem/u:SI (plus:SI (reg:SI 13 %a5) (const:SI (unspec:SI [ (symbol_ref:SI ("__gcov_kvp_dynamic_pool_index") [flags 0x40] <var_decl 0x7f9e83fe7cf0 __gcov_kvp_dynamic_pool_index>) (const_int 0 [0]) ] 6))) [0 S4 A8])) "gcc/libgcc/libgcov.h":472:44 55 {*movsi_m68k2} (expr_list:REG_EQUAL (symbol_ref:SI ("__gcov_kvp_dynamic_pool_index") [flags 0x40] <var_decl 0x7f9e83fe7cf0 __gcov_kvp_dynamic_pool_index>) (nil))) Wrapping symbolic expressions into the unspec was added in the commit that implemented TLS for m68k, but the 'CONST' case in the predicate code was not updated to filter wrapped expressions out.
next prev parent reply other threads:[~2022-11-11 18:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-11 16:53 [Bug target/107645] New: " jcmvbkbc at gcc dot gnu.org 2022-11-11 18:54 ` jcmvbkbc at gcc dot gnu.org [this message] 2022-11-16 12:36 ` [Bug target/107645] " cvs-commit at gcc dot gnu.org 2022-11-16 12:38 ` jcmvbkbc at gcc dot gnu.org 2022-11-28 22:23 ` 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-107645-4-BYcYGFTs7Q@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: linkBe 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).