public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/111475] [14 regression] Many C++ analyzer tests FAIL Date: Tue, 23 Apr 2024 17:16:51 +0000 [thread overview] Message-ID: <bug-111475-4-8KFHf9NJrm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111475-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111475 Rainer Orth <ro at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2024-04-23 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #7 from Rainer Orth <ro at gcc dot gnu.org> --- A reghunt identified this patch as the culprit: commit 55f6a7d949abc708d1c6ebc01eb3053f96d1472b Author: benjamin priour <vultkayn@gcc.gnu.org> Date: Sun Aug 27 14:36:14 2023 +0200 analyzer: Move gcc.dg/analyzer tests to c-c++-common (1) [PR96395]
next prev parent reply other threads:[~2024-04-23 17:16 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-19 11:50 [Bug analyzer/111475] New: " ro at gcc dot gnu.org 2023-09-19 11:51 ` [Bug analyzer/111475] " ro at gcc dot gnu.org 2024-01-18 12:52 ` ro at gcc dot gnu.org 2024-01-18 15:16 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-01-19 10:10 ` ro at gcc dot gnu.org 2024-01-19 10:11 ` ro at gcc dot gnu.org 2024-01-19 10:11 ` ro at gcc dot gnu.org 2024-04-23 13:46 ` [Bug analyzer/111475] [14 regression] " ro at gcc dot gnu.org 2024-04-23 17:16 ` ro at gcc dot gnu.org [this message] 2024-04-26 13:06 ` [Bug analyzer/111475] [14/15 " ro at gcc dot gnu.org 2024-04-26 13:15 ` dmalcolm at gcc dot gnu.org 2024-04-26 13:36 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-04-30 19:43 ` dmalcolm at gcc dot gnu.org 2024-05-01 10:29 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-05-03 13:12 ` cvs-commit at gcc dot gnu.org 2024-05-03 13:34 ` [Bug analyzer/111475] [14 " dmalcolm at gcc dot gnu.org 2024-05-06 8:55 ` cvs-commit 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-111475-4-8KFHf9NJrm@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).