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 c/114931] [14/15 regression] ICE in get_alias_set when building tcl with -std=c23 Date: Fri, 03 May 2024 07:11:10 +0000 [thread overview] Message-ID: <bug-114931-4-B5V9kjNBZH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114931-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114931 --- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> --- When we build the pointer type there's already (gdb) p to_type $18 = <function_type 0x7ffff6b7d930> (gdb) p to_type->type_common.canonical $15 = <function_type 0x7ffff6b7d690> (gdb) p to_type->type_common.canonical->type_common.canonical $17 = <tree 0x0> the interesting bit is that build_function_type when doing else if (any_noncanonical_p) TYPE_CANONICAL (t) = build_function_type (TYPE_CANONICAL (value_type), canon_argtypes); to build the canonical type gets an already present function type through type_has_canon that has TYPE_STRUCTURAL_EQUALITY_P set. So somehow it is inconsistent with itself here - at the time we build that function type maybe_canonicalize_argtypes sets any_structural_p so it seems we set TYPE_CANONICAL "late" on some types? In particular both the pointer and struct type have TYPE_STRUCTURAL_EQUALITY_P set. It might be tempting to do the following which fixes the testcase but then this simply means we'll never find types with structural equality in the hash (note we insert those when they still have themselves as canonical type). In some sense TYPE_STRUCTURAL_EQUALITY_P means we have not properly unified types so unifying even less shouldn't make it much worse. It would be still interesting to see why we build the function type with original "incomplete" argument types. diff --git a/gcc/tree.cc b/gcc/tree.cc index 83f3bf306af..35bb7713e1f 100644 --- a/gcc/tree.cc +++ b/gcc/tree.cc @@ -6109,6 +6109,10 @@ type_cache_hasher::equal (type_hash *a, type_hash *b) || TYPE_MODE (a->type) != TYPE_MODE (b->type))) return false; + if (TYPE_STRUCTURAL_EQUALITY_P (a->type) + != TYPE_STRUCTURAL_EQUALITY_P (b->type)) + return false; + switch (TREE_CODE (a->type)) { case VOID_TYPE: debugging patch: diff --git a/gcc/tree.cc b/gcc/tree.cc index 83f3bf306af..35bb7713e1f 100644 --- a/gcc/tree.cc +++ b/gcc/tree.cc @@ -7520,8 +7524,11 @@ build_function_type (tree value_type, tree arg_types, if (any_structural_p) SET_TYPE_STRUCTURAL_EQUALITY (t); else if (any_noncanonical_p) + { TYPE_CANONICAL (t) = build_function_type (TYPE_CANONICAL (value_type), canon_argtypes); + gcc_assert (TYPE_CANONICAL (TYPE_CANONICAL (t)) == TYPE_CANONICAL (t)); + } if (!COMPLETE_TYPE_P (t)) layout_type (t);
next prev parent reply other threads:[~2024-05-03 7:11 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-03 2:37 [Bug rtl-optimization/114931] New: " sjames at gcc dot gnu.org 2024-05-03 2:38 ` [Bug rtl-optimization/114931] " sjames at gcc dot gnu.org 2024-05-03 2:43 ` [Bug c/114931] " pinskia at gcc dot gnu.org 2024-05-03 2:52 ` pinskia at gcc dot gnu.org 2024-05-03 3:10 ` sjames at gcc dot gnu.org 2024-05-03 6:34 ` [Bug c/114931] [14/15 regression] " rguenth at gcc dot gnu.org 2024-05-03 7:11 ` rguenth at gcc dot gnu.org [this message] 2024-05-03 7:16 ` rguenth at gcc dot gnu.org 2024-05-03 7:25 ` rguenth at gcc dot gnu.org 2024-05-03 7:41 ` jakub at gcc dot gnu.org 2024-05-03 7:56 ` rguenth at gcc dot gnu.org 2024-05-03 8:22 ` rguenth at gcc dot gnu.org 2024-05-03 8:25 ` jakub at gcc dot gnu.org 2024-05-03 9:01 ` rguenth at gcc dot gnu.org 2024-05-03 9:05 ` rguenth at gcc dot gnu.org 2024-05-03 9:50 ` rguenth at gcc dot gnu.org 2024-05-03 11:01 ` cvs-commit at gcc dot gnu.org 2024-05-07 7:46 ` rguenth at gcc dot gnu.org 2024-05-07 11:05 ` cvs-commit at gcc dot gnu.org 2024-05-07 11:07 ` [Bug c/114931] [14 " rguenth at gcc dot gnu.org 2024-05-07 12:30 ` rguenth at gcc dot gnu.org 2024-05-07 18:10 ` sjames at gcc dot gnu.org 2024-05-15 16:09 ` cvs-commit at gcc dot gnu.org 2024-05-15 16:09 ` cvs-commit at gcc dot gnu.org 2024-05-15 16:09 ` 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-114931-4-B5V9kjNBZH@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).