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 debug/113394] ICE: 'verify_type' failed: type variant with 'TYPE_ALIAS_SET_KNOWN_P' with -fstrub=internal -g
Date: Wed, 31 Jan 2024 03:24:33 +0000	[thread overview]
Message-ID: <bug-113394-4-zogu707Sb5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113394-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Alexandre Oliva <aoliva@gcc.gnu.org>:

https://gcc.gnu.org/g:d826596acb02edf41ac4f76af2aed5efa3b8c698

commit r14-8643-gd826596acb02edf41ac4f76af2aed5efa3b8c698
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Wed Jan 31 00:13:27 2024 -0300

    strub: drop nonaliased parm from build_ref_type_for [PR113394]

    Variant type copies can't have their own alias sets any more, and it's
    not like setting them affected the pointed-to objects anyway.


    for  gcc/ChangeLog

            PR debug/113394
            * ipa-strub.cc (build_ref_type_for): Drop nonaliased.  Adjust
            caller.

    for  gcc/testsuite/ChangeLog

            PR debug/113394
            * gcc.dg/strub-internal-pr113394.c: New.

  parent reply	other threads:[~2024-01-31  3:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15  6:28 [Bug rtl-optimization/113394] New: " zsojka at seznam dot cz
2024-01-29 19:03 ` [Bug debug/113394] " aoliva at gcc dot gnu.org
2024-01-31  3:24 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-31  3:37 ` aoliva 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-113394-4-zogu707Sb5@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).