public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104620] FAIL: g++.dg/cpp23/consteval-if2.C -std=gnu++20 (test for errors) Date: Wed, 23 Mar 2022 18:04:47 +0000 [thread overview] Message-ID: <bug-104620-4-3fMRNNuB6j@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104620-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104620 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Host|hppa*-*-linux* | CC| |mpolacek at gcc dot gnu.org Ever confirmed|0 |1 Last reconfirmed| |2022-03-23 Status|UNCONFIRMED |NEW Target|hppa*-*-linux* | Build|hppa*-*-linux* | --- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> --- I see it on x86_64 too. Confirmed.
next prev parent reply other threads:[~2022-03-23 18:04 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-21 19:38 [Bug c++/104620] New: " danglin at gcc dot gnu.org 2022-03-23 18:04 ` mpolacek at gcc dot gnu.org [this message] 2022-03-23 18:42 ` [Bug c++/104620] " mpolacek at gcc dot gnu.org 2022-03-23 20:35 ` ppalka at gcc dot gnu.org 2022-03-24 12:21 ` jakub at gcc dot gnu.org 2022-03-24 13:29 ` jakub at gcc dot gnu.org 2022-03-24 13:31 ` ppalka at gcc dot gnu.org 2022-03-24 13:37 ` ppalka at gcc dot gnu.org 2022-03-24 14:29 ` ppalka at gcc dot gnu.org 2022-03-24 15:21 ` jason at gcc dot gnu.org 2022-03-24 15:42 ` cvs-commit at gcc dot gnu.org 2022-03-24 17:19 ` ppalka at gcc dot gnu.org 2022-03-26 23:01 ` jason at gcc dot gnu.org 2022-05-06 8:32 ` jakub at gcc dot gnu.org 2023-05-08 12:23 ` 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-104620-4-3fMRNNuB6j@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).