public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/114931] [14 regression] ICE in get_alias_set when building tcl with -std=c23
Date: Wed, 15 May 2024 16:09:10 +0000 [thread overview]
Message-ID: <bug-114931-4-DGMKSX50me@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 #21 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-14 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:573e1df0ec8428e564c97af7c237a5e0c98c59bd
commit r14-10210-g573e1df0ec8428e564c97af7c237a5e0c98c59bd
Author: Richard Biener <rguenther@suse.de>
Date: Fri May 3 11:48:07 2024 +0200
Avoid changing type in the type_hash_canon hash
When building a type and type_hash_canon returns an existing type
avoid changing it, in particular its TYPE_CANONICAL.
PR middle-end/114931
* tree.cc (build_array_type_1): Return early when type_hash_canon
returned an older existing type.
(build_function_type): Likewise.
(build_method_type_directly): Likewise.
(build_offset_type): Likewise.
(cherry picked from commit 7a212ac678e13e0df5da2d090144b246a1262b64)
next prev parent reply other threads:[~2024-05-15 16:09 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
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 [this message]
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-DGMKSX50me@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).