public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vultkayn at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/110198] [14 regression] g++.dg/analyzer/pr100244.C fails after r14-1632-g9589a46ddadc8b
Date: Fri, 09 Jun 2023 22:30:56 +0000	[thread overview]
Message-ID: <bug-110198-4-9eB5QRv4Fh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110198-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110198

--- Comment #2 from Benjamin Priour <vultkayn at gcc dot gnu.org> ---
Yes sorry for the regression. I confirmed it myself too on x86_64-linux-gnu.
I wrote a fix immediately yesterday, and I am currently regtesting it.

It is promising as I quickly ran the test only for the analyzer test cases, all
of them now are back to their expected behavior.

I'm sending the patch as soon as the regtesting finishes, so probably tomorrow
evening, as my keys on the compiler farm are not yet synced.

For pr101962.c, it was indeed just a now obsolete message that had to be
removed.

For pr100244.C it required to change the way OOB are handled by the
uninitialized-value checker.

  parent reply	other threads:[~2023-06-09 22:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 19:13 [Bug other/110198] New: " seurer at gcc dot gnu.org
2023-06-09 22:12 ` [Bug other/110198] " pinskia at gcc dot gnu.org
2023-06-09 22:30 ` vultkayn at gcc dot gnu.org [this message]
2023-06-20 14:37 ` [Bug analyzer/110198] " hp at gcc dot gnu.org
2023-06-20 14:45 ` priour.be at gmail dot com
2023-06-22 14:33 ` hp at gcc dot gnu.org
2023-06-29 23:35 ` cvs-commit at gcc dot gnu.org
2023-06-29 23:39 ` vultkayn 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-110198-4-9eB5QRv4Fh@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: link
Be 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).