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++/113545] ICE in label_matches with constexpr function with switch-statement and converted (nonconstant, cast address) input Date: Sat, 10 Feb 2024 03:41:52 +0000 [thread overview] Message-ID: <bug-113545-4-86OUEtV2YJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113545-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113545 --- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Hans-Peter Nilsson <hp@gcc.gnu.org>: https://gcc.gnu.org/g:48207a5f00d6ae7cb11038e7c17f6858de4a884e commit r14-8907-g48207a5f00d6ae7cb11038e7c17f6858de4a884e Author: Hans-Peter Nilsson <hp@axis.com> Date: Mon Jan 22 01:09:03 2024 +0100 c++: testcases for PR113545 (constexpr with switch and passing non-constexpr parameter) Test-cases, with constexpr-reinterpret3.C dg-ice:ing the PR c++/113545 bug. Regarding the request in the comment, A dg-do run when there's an ICE will cause some CI's to signal an error for the run being "UNRESOLVED" (compilation failed to produce executable). Note that dejagnu (1.6.3) itself doesn't consider this an error. gcc/testsuite: PR c++/113545 * g++.dg/cpp1y/constexpr-reinterpret3.C, g++.dg/cpp1y/constexpr-reinterpret4.C: New tests.
next prev parent reply other threads:[~2024-02-10 3:41 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-22 16:53 [Bug c++/113545] New: " hp at gcc dot gnu.org 2024-01-22 17:21 ` [Bug c++/113545] " hp at gcc dot gnu.org 2024-02-07 0:31 ` hp at gcc dot gnu.org 2024-02-07 0:32 ` hp at gcc dot gnu.org 2024-02-10 3:41 ` cvs-commit at gcc dot gnu.org [this message] 2024-02-12 19:56 ` cvs-commit at gcc dot gnu.org 2024-02-12 20:02 ` mpolacek at gcc dot gnu.org 2024-02-14 1:17 ` hp at gcc dot gnu.org 2024-02-16 17:30 ` cvs-commit at gcc dot gnu.org 2024-02-16 17:30 ` mpolacek 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-113545-4-86OUEtV2YJ@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).