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++/109666] [13/14 Regression] Segmentation fault with std::array using gcc 13 since r13-6788
Date: Tue, 02 May 2023 20:25:57 +0000	[thread overview]
Message-ID: <bug-109666-4-UYndbO6Seo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109666-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:

https://gcc.gnu.org/g:0a2c771910e888c9a26db319122230144789b9bf

commit r13-7278-g0a2c771910e888c9a26db319122230144789b9bf
Author: Jason Merrill <jason@redhat.com>
Date:   Mon May 1 10:57:20 2023 -0400

    c++: array DMI and member fn [PR109666]

    Here it turns out I also needed to adjust cfun when stepping out of the
    member function to instantiate the DMI.  But instead of adding that tweak,
    let's unify with instantiate_body and just push_to_top_level instead of
    trying to do the minimum subset of it.  There was no measurable change in
    compile time on stdc++.h.

    This should also resolve 109506 without yet another tweak.

            PR c++/109666

    gcc/cp/ChangeLog:

            * name-lookup.cc (maybe_push_to_top_level)
            (maybe_pop_from_top_level): Split out...
            * pt.cc (instantiate_body): ...from here.
            * init.cc (maybe_instantiate_nsdmi_init): Use them.
            * name-lookup.h: Declare them..

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/nsdmi-array2.C: New test.

  parent reply	other threads:[~2023-05-02 20:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 11:41 [Bug c++/109666] New: Segmentation fault with std::array using gcc 13 john.viklund at effnet dot com
2023-04-28 12:18 ` [Bug c++/109666] [13/14 Regression] " redi at gcc dot gnu.org
2023-04-28 12:22 ` redi at gcc dot gnu.org
2023-04-28 14:20 ` mpolacek at gcc dot gnu.org
2023-04-28 14:21 ` mpolacek at gcc dot gnu.org
2023-05-01 14:25 ` [Bug c++/109666] [13/14 Regression] Segmentation fault with std::array using gcc 13 since r13-6788 jason at gcc dot gnu.org
2023-05-01 20:55 ` cvs-commit at gcc dot gnu.org
2023-05-02  7:19 ` carlosgalvezp at gmail dot com
2023-05-02 20:25 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-03 17:11 ` jason at gcc dot gnu.org
2023-05-04 14:30 ` [Bug c++/109666] [12 Regression] Segmentation fault with std::array jason at gcc dot gnu.org
2023-05-04 14:48 ` cvs-commit at gcc dot gnu.org
2023-05-04 20:04 ` pinskia at gcc dot gnu.org
2023-05-08 12:27 ` rguenth at gcc dot gnu.org
2023-05-08 12:44 ` rguenth at gcc dot gnu.org
2023-05-09 11:30 ` marxin at gcc dot gnu.org
2023-08-11 21:21 ` cvs-commit at gcc dot gnu.org
2023-09-11 22:11 ` 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-109666-4-UYndbO6Seo@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).