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:15 +0000	[thread overview]
Message-ID: <bug-114931-4-UxSBSXSz6w@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 #22 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:1d89cb43943e77d0bbb48fd5a58a352bdd3d82c7

commit r14-10211-g1d89cb43943e77d0bbb48fd5a58a352bdd3d82c7
Author: Richard Biener <rguenther@suse.de>
Date:   Fri May 3 10:44:50 2024 +0200

    middle-end/114931 - type_hash_canon and structual equality types

    TYPE_STRUCTURAL_EQUALITY_P is part of our type system so we have
    to make sure to include that into the type unification done via
    type_hash_canon.  This requires the flag to be set before querying
    the hash which is the biggest part of the patch.

            PR middle-end/114931
    gcc/
            * tree.cc (type_hash_canon_hash): Hash TYPE_STRUCTURAL_EQUALITY_P.
            (type_cache_hasher::equal): Compare TYPE_STRUCTURAL_EQUALITY_P.
            (build_array_type_1): Set TYPE_STRUCTURAL_EQUALITY_P before
            probing with type_hash_canon.
            (build_function_type): Likewise.
            (build_method_type_directly): Likewise.
            (build_offset_type): Likewise.
            (build_complex_type): Likewise.
            * attribs.cc (build_type_attribute_qual_variant): Likewise.

    gcc/c-family/
            * c-common.cc (complete_array_type): Set TYPE_STRUCTURAL_EQUALITY_P
            before probing with type_hash_canon.

    gcc/testsuite/
            * gcc.dg/pr114931.c: New testcase.

    (cherry picked from commit b09c2e9560648b0cf993c2ca9ad972c34e6bddfa)

  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
2024-05-15 16:09 ` cvs-commit at gcc dot gnu.org [this message]
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-UxSBSXSz6w@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).