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++/102338] [9/10/11/12 Regression] Recursive noexcept specification inside class/struct Date: Thu, 20 Jan 2022 20:03:32 +0000 [thread overview] Message-ID: <bug-102338-4-tb06dg4Sd1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102338-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102338 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:30b38394b482ce894d9bc81731a0eea8711f4587 commit r12-6778-g30b38394b482ce894d9bc81731a0eea8711f4587 Author: Marek Polacek <polacek@redhat.com> Date: Thu Jan 20 15:00:11 2022 -0500 c++: Add test for fixed PR [PR102338] This was fixed by r12-6025 and is sufficiently different from noexcept71.C that I think we should add it. PR c++/102338 gcc/testsuite/ChangeLog: * g++.dg/cpp1y/noexcept2.C: New test.
next prev parent reply other threads:[~2022-01-20 20:03 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-15 7:19 [Bug c++/102338] New: " jergussuja at gmail dot com 2021-09-15 7:21 ` [Bug c++/102338] " jergussuja at gmail dot com 2021-09-15 7:22 ` jergussuja at gmail dot com 2021-09-15 7:23 ` jergussuja at gmail dot com 2021-09-15 7:28 ` jergussuja at gmail dot com 2021-09-15 7:46 ` pinskia at gcc dot gnu.org 2021-09-15 7:47 ` pinskia at gcc dot gnu.org 2021-09-15 7:50 ` pinskia at gcc dot gnu.org 2021-09-15 8:04 ` [Bug c++/102338] [9/10/11/12 Regression] " rguenth at gcc dot gnu.org 2022-01-20 19:09 ` ppalka at gcc dot gnu.org 2022-01-20 19:29 ` mpolacek at gcc dot gnu.org 2022-01-20 20:03 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-20 20:06 ` [Bug c++/102338] [9/10/11 " mpolacek at gcc dot gnu.org 2022-01-21 1:55 ` pinskia 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-102338-4-tb06dg4Sd1@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: linkBe 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).