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:16:11 +0000 [thread overview] Message-ID: <bug-114931-4-QnTYO4T2Am@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- I'll note that seeing code like the following which possibly mutates existing hash entries looks quite broken. But of course type_hash_canon is a fragile bit of code (well, it shouldn't ...). To me it looks like we should compute and set the canonical type first and _then_ do the hash lookup (which should include the canonical type). And I'd make type_hash_canon take a tree * to modify, making its return value a bool whether we found an existing type so we can simply do if (type_hash_canon (hash, &t)) { ggc_free (orig_t); return t; } tree build_function_type (tree value_type, tree arg_types, bool no_named_args_stdarg_p) { tree t; inchash::hash hstate; bool any_structural_p, any_noncanonical_p; tree canon_argtypes; gcc_assert (arg_types != error_mark_node); if (TREE_CODE (value_type) == FUNCTION_TYPE) { error ("function return type cannot be function"); value_type = integer_type_node; } /* Make a node of the sort we want. */ t = make_node (FUNCTION_TYPE); TREE_TYPE (t) = value_type; TYPE_ARG_TYPES (t) = arg_types; if (no_named_args_stdarg_p) { gcc_assert (arg_types == NULL_TREE); TYPE_NO_NAMED_ARGS_STDARG_P (t) = 1; } /* If we already have such a type, use the old one. */ hashval_t hash = type_hash_canon_hash (t); t = type_hash_canon (hash, t); /* Set up the canonical type. */ any_structural_p = TYPE_STRUCTURAL_EQUALITY_P (value_type); any_noncanonical_p = TYPE_CANONICAL (value_type) != value_type; canon_argtypes = maybe_canonicalize_argtypes (arg_types, &any_structural_p, &any_noncanonical_p); 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); if (!COMPLETE_TYPE_P (t)) layout_type (t); return t; }
next prev parent reply other threads:[~2024-05-03 7:16 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 2024-05-03 7:16 ` rguenth at gcc dot gnu.org [this message] 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-QnTYO4T2Am@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).