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 ipa/114930] [14/15 regression] ICE in fld_incomplete_type_of when building libwebp with -std=c23 -flto
Date: Tue, 21 May 2024 08:50:07 +0000	[thread overview]
Message-ID: <bug-114930-4-ZUT2ToBRlG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114930-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114930

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu.org

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Likely an issue in fld_incomplete_type_of with how C23 lays out types and/or
how we set up their canonical types.  What we try to do for LTO is to
turn pointer types to pointer types to pointer to "incomplete" type variants,
thus for arrays to [] and for structs to structs with no fields.

Somebody needs to see how it goes wrong, the assert makes sense and is required
for correctness.

  parent reply	other threads:[~2024-05-21  8:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03  1:19 [Bug ipa/114930] New: " sjames at gcc dot gnu.org
2024-05-03  1:40 ` [Bug ipa/114930] " sjames at gcc dot gnu.org
2024-05-03  1:41 ` pinskia at gcc dot gnu.org
2024-05-03  2:55 ` [Bug ipa/114930] [14/15 regression] " sjames at gcc dot gnu.org
2024-05-03  6:32 ` rguenth at gcc dot gnu.org
2024-05-07  7:46 ` rguenth at gcc dot gnu.org
2024-05-18 15:44 ` sjames at gcc dot gnu.org
2024-05-21  8:50 ` rguenth at gcc dot gnu.org [this message]
2024-06-02 10:16 ` [Bug c/114930] " uecker at gcc dot gnu.org
2024-06-12 14:25 ` sjames at gcc dot gnu.org
2024-06-25  6:37 ` cvs-commit 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-114930-4-ZUT2ToBRlG@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).