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 ipa/106124] [11 Regression] ICE in dwarf2out_abstract_function, at dwarf2out.cc:23254
Date: Tue, 02 May 2023 12:03:33 +0000	[thread overview]
Message-ID: <bug-106124-4-NeAnjCAes8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106124-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:1cfc7f22eb4587029624050006c2ab4e82e9a0b1

commit r11-10672-g1cfc7f22eb4587029624050006c2ab4e82e9a0b1
Author: Richard Biener <rguenther@suse.de>
Date:   Mon Mar 27 16:40:15 2023 +0200

    ipa/106124 - ICE with -fkeep-inline-functions and OpenMP

    The testcases in this bug reveal cases where an early generated
    type is collected because it was unused but gets attempted to
    be recreated later when a late DIE for a function (an OpenMP
    reduction) is created.  That's unexpected and possibly the fault
    of OpenMP but the following allows the re-creation of the context
    type to succeed.

            PR ipa/106124
            * dwarf2out.c (lookup_type_die): Reset TREE_ASM_WRITTEN
            so we can re-create the DIE for the type if required.

            * g++.dg/gomp/pr106124.C: New testcase.

    (cherry picked from commit 36330e2e95564a360e6dbcfb4e7566d5c2177415)

  parent reply	other threads:[~2023-05-02 12:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 17:11 [Bug c++/106124] New: [11/12/13 " gscfq@t-online.de
2022-06-28 18:45 ` [Bug ipa/106124] " marxin at gcc dot gnu.org
2022-06-29  9:45 ` rguenth at gcc dot gnu.org
2022-06-29 11:23 ` jakub at gcc dot gnu.org
2023-03-27 14:37 ` rguenth at gcc dot gnu.org
2023-03-28 14:58 ` jakub at gcc dot gnu.org
2023-03-29  6:46 ` rguenther at suse dot de
2023-03-29  6:56 ` cvs-commit at gcc dot gnu.org
2023-03-29  6:57 ` [Bug ipa/106124] [11/12 " rguenth at gcc dot gnu.org
2023-04-17  9:14 ` cvs-commit at gcc dot gnu.org
2023-05-02 12:03 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-02 12:05 ` [Bug ipa/106124] [11 " 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-106124-4-NeAnjCAes8@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).