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 tree-optimization/101494] [11 Regression] -Wmaybe-uninitialized false alarm with memrchr of size 0
Date: Wed, 28 Jul 2021 22:27:07 +0000 [thread overview]
Message-ID: <bug-101494-4-U52yaxA2Bp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101494-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101494
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>:
https://gcc.gnu.org/g:1121e495b70105deeb82295f8210e30f2080bc37
commit r12-2583-g1121e495b70105deeb82295f8210e30f2080bc37
Author: Martin Sebor <msebor@redhat.com>
Date: Wed Jul 28 16:25:40 2021 -0600
Correct uninitialized object offset and size computation [PR101494].
Resolves:
PR middle-end/101494 - -Wuninitialized false alarm with memrchr of size 0
gcc/ChangeLog:
PR middle-end/101494
* tree-ssa-uninit.c (maybe_warn_operand): Correct object offset
and size computation.
gcc/testsuite/ChangeLog:
PR middle-end/101494
* gcc.dg/uninit-pr101494.c: New test.
next prev parent reply other threads:[~2021-07-28 22:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 2:08 [Bug tree-optimization/101494] New: " eggert at cs dot ucla.edu
2021-07-18 9:18 ` [Bug tree-optimization/101494] " bruno at clisp dot org
2021-07-21 18:05 ` msebor at gcc dot gnu.org
2021-07-21 18:09 ` [Bug tree-optimization/101494] [11 Regression] " msebor at gcc dot gnu.org
2021-07-22 23:06 ` msebor at gcc dot gnu.org
2021-07-28 7:07 ` rguenth at gcc dot gnu.org
2021-07-28 22:27 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-28 22:27 ` msebor at gcc dot gnu.org
2022-04-21 7:49 ` rguenth at gcc dot gnu.org
2023-05-29 10:05 ` jakub 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-101494-4-U52yaxA2Bp@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).