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/102360] ICE in can_native_interpret_type_p at gcc/fold-const.c:8800 Date: Thu, 16 Sep 2021 09:18:51 +0000 [thread overview] Message-ID: <bug-102360-4-71JGG6VRuq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102360-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102360 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Last reconfirmed| |2021-09-16 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. Program received signal SIGSEGV, Segmentation fault. 0x00000000012f2e6b in can_native_interpret_type_p (type=<tree 0x0>) at ../../src/trunk/gcc/fold-const.c:8800 8800 switch (TREE_CODE (type)) 3049 if (!can_native_interpret_type_p (var_type)) 3050 { 3051 alt_type 3052 = lang_hooks.types.type_for_mode (TYPE_MODE (var_type), 3053 TYPE_UNSIGNED (var_type)); 3054 gcc_assert (can_native_interpret_type_p (alt_type)); 3055 } alt_type doesn't need to exist. TYPE_MODE is OImode here. Another issue will be that native_interpret_int refuses to interpret types bigger than 128bit. So using alt_type = build_nonstandard_integer_type (GET_MODE_BITSIZE (TYPE_MODE (var_type)), 1); will likely not help. But if we know we're using an integer type we can natively interpret ourselves. Note there's another hole with variable-size and SVE vector modes I think. I'm testing something.
next prev parent reply other threads:[~2021-09-16 9:18 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-16 8:56 [Bug tree-optimization/102360] New: " marxin at gcc dot gnu.org 2021-09-16 8:56 ` [Bug tree-optimization/102360] " marxin at gcc dot gnu.org 2021-09-16 9:18 ` rguenth at gcc dot gnu.org [this message] 2021-09-16 11:23 ` cvs-commit at gcc dot gnu.org 2021-09-16 11:23 ` 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-102360-4-71JGG6VRuq@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).