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++/109506] [10/11/12/13 regression] -fchecking=2 causes some template constructor not be instantiated when used with NSDMI
Date: Fri, 05 May 2023 15:22:20 +0000	[thread overview]
Message-ID: <bug-109506-4-kRD524s2s5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109506-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Patrick Palka
<ppalka@gcc.gnu.org>:

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

commit r13-7300-gf077b784a6e6876682606bd788ac77a698b81016
Author: Patrick Palka <ppalka@redhat.com>
Date:   Tue May 2 08:48:59 2023 -0400

    c++: Add testcase for already fixed PR [PR109506]

    The PR109666 fix r14-386-g07c52d1eec967 incidentally also fixes this PR.

            PR c++/109506

    gcc/testsuite/ChangeLog:

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

    (cherry picked from commit 9a9840cedbdc8be8252fd8f2d31d8fbd36632a2e)

  parent reply	other threads:[~2023-05-05 15:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13 21:31 [Bug c++/109506] New: [13 regression] 'error: inlining failed in call to ‘always_inline’ ‘foo<T>::foo() [with T = void]’: function body not available' sjames at gcc dot gnu.org
2023-04-13 21:38 ` [Bug c++/109506] " pinskia at gcc dot gnu.org
2023-04-13 21:41 ` pinskia at gcc dot gnu.org
2023-04-13 21:50 ` mpolacek at gcc dot gnu.org
2023-04-13 21:56 ` pinskia at gcc dot gnu.org
2023-04-13 21:57 ` pinskia at gcc dot gnu.org
2023-04-13 22:01 ` [Bug c++/109506] [10/11/12/13 regression] -fchecking=2 causes some template constructor not be instantiated when used with NSDMI pinskia at gcc dot gnu.org
2023-04-13 22:18 ` pinskia at gcc dot gnu.org
2023-04-13 22:19 ` pinskia at gcc dot gnu.org
2023-04-15  1:15 ` sjames at gcc dot gnu.org
2023-04-17 17:33 ` [Bug c++/109506] [10/11/12/13/14 " ppalka at gcc dot gnu.org
2023-04-27 15:20 ` ppalka at gcc dot gnu.org
2023-05-02 12:49 ` cvs-commit at gcc dot gnu.org
2023-05-05 15:22 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-07 10:45 ` [Bug c++/109506] [11/12 " rguenth at gcc dot gnu.org
2023-08-11 19:19 ` jason 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-109506-4-kRD524s2s5@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).