public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110896] New: [12/13/14 Regression] gcc.dg/ubsan/pr81981.c is xfailed Date: Thu, 03 Aug 2023 22:46:49 +0000 [thread overview] Message-ID: <bug-110896-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110896 Bug ID: 110896 Summary: [12/13/14 Regression] gcc.dg/ubsan/pr81981.c is xfailed Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: diagnostic, xfail Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Blocks: 24639 Target Milestone: --- The original issue in PR 81981 is fixed. The problem here is we don't even warn without -fsanitize=undefined too. Testcase from that PR: ``` int foo (int i) { int t[1], u[1]; int n = 0; if (i) { t[n] = i; u[0] = i; } return t[0] + u[0]; } ``` we don't warn about `u[0]` being unintinialized with just `-O2 -Wall -Wextra` starting in GCC 12 via r12-4625 (the fix for pr102681). That is the issue is unrelated to -fsanitize=undefined now. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 [Bug 24639] [meta-bug] bug to track all Wuninitialized issues
next reply other threads:[~2023-08-03 22:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-03 22:46 pinskia at gcc dot gnu.org [this message] 2023-08-03 22:47 ` [Bug tree-optimization/110896] " pinskia at gcc dot gnu.org 2023-08-04 7:07 ` rguenth at gcc dot gnu.org 2024-03-07 23:26 ` law 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-110896-4@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).