public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97399] [10 Regression] g++ 9.3 cannot compile SFINAE code with separated declaration and definition, g++ 7.3 compiles Date: Fri, 07 Jul 2023 09:08:17 +0000 [thread overview] Message-ID: <bug-97399-4-59b4LracEP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97399-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97399 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |10.5.0 Known to work| |11.1.0 Status|ASSIGNED |RESOLVED Target Milestone|10.5 |11.0 Resolution|--- |FIXED --- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> --- Fixed for GCC 11.
prev parent reply other threads:[~2023-07-07 9:08 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-13 9:58 [Bug c++/97399] New: " renlin at gcc dot gnu.org 2020-10-13 9:58 ` [Bug c++/97399] " renlin at gcc dot gnu.org 2020-10-13 11:02 ` [Bug c++/97399] [9/10/11 Regression] " rguenth at gcc dot gnu.org 2020-10-13 14:10 ` marxin at gcc dot gnu.org 2021-01-14 9:25 ` rguenth at gcc dot gnu.org 2021-01-20 20:00 ` ppalka at gcc dot gnu.org 2021-01-23 5:25 ` cvs-commit at gcc dot gnu.org 2021-01-23 5:25 ` [Bug c++/97399] [9/10 " ppalka at gcc dot gnu.org 2021-04-10 20:33 ` cvs-commit at gcc dot gnu.org 2021-06-01 8:18 ` rguenth at gcc dot gnu.org 2022-05-27 9:43 ` [Bug c++/97399] [10 " rguenth at gcc dot gnu.org 2022-06-28 10:42 ` jakub at gcc dot gnu.org 2023-07-07 9:08 ` rguenth at gcc dot gnu.org [this message]
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-97399-4-59b4LracEP@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).