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:56:45 +0000	[thread overview]
Message-ID: <bug-114931-4-LcNFI8Ke2j@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 #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #9)
> Do you really need to hash it on TYPE_CANON, rather than just on whether the
> type is
> TYPE_STRUCTURAL_EQUALITY_P or not?

It's enough for the testcases here, I didn't try to convince myself it's safe
but of course it's better than what we do right now.  So we can try that as
well.

> I'm worried that always computing the TYPE_CANON before calling
> type_hash_canon is going to be quite expensive, while just figuring out if
> it should have TYPE_STRUCTURAL_EQUALITY_P or not should be cheaper.  If it
> should have
> TYPE_STRUCTURAL_EQUALITY_P, we'd SET_TYPE_STRUCTURAL_EQUALITY, otherwise set
> TYPE_CANONICAL (t) = t; (I think that is what we generally get from
> make_node), look up
> and recompute TYPE_CANONICAL if TYPE_CANONICAL (t) == t.

I'd like to make it obvious at least that we only alter TYPE_CANONICAL if
we were the one building 't' in the first place.  The layouting of types
also seems to be redundant now as that's done by type_hash_canon.

Luckily there are not too many callers.

It's a bit late for 14.1, so we can refactor things on trunk and then backport
later.

  parent reply	other threads:[~2024-05-03  7:56 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 [this message]
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-LcNFI8Ke2j@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).