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/101912] -Wmaybe-uninitialized false alarm in tzdb localtime.c Date: Mon, 09 Jan 2023 11:19:10 +0000 [thread overview] Message-ID: <bug-101912-4-s29J8irA1y@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101912-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101912 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:7afecddf1ecbb93ee44517ad6d3e9c1c0d68e722 commit r13-5064-g7afecddf1ecbb93ee44517ad6d3e9c1c0d68e722 Author: Richard Biener <rguenther@suse.de> Date: Mon Jan 9 11:00:43 2023 +0100 tree-optimization/101912 - testcase for fixed uninit case We now properly optimize this testcase and no longer diagnose a bogus uninit use. PR tree-optimization/101912 * gcc.dg/uninit-pr101912.c: New testcase.
next prev parent reply other threads:[~2023-01-09 11:19 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-14 19:27 [Bug tree-optimization/101912] New: " eggert at cs dot ucla.edu 2021-08-16 17:07 ` [Bug tree-optimization/101912] " msebor at gcc dot gnu.org 2021-11-30 15:41 ` aldyh at gcc dot gnu.org 2021-11-30 16:02 ` aldyh at gcc dot gnu.org 2021-11-30 16:47 ` eggert at cs dot ucla.edu 2021-12-01 7:49 ` rguenther at suse dot de 2021-12-01 16:22 ` aldyh at gcc dot gnu.org 2022-12-25 0:06 ` pinskia at gcc dot gnu.org 2022-12-27 12:26 ` marxin at gcc dot gnu.org 2023-01-09 10:02 ` rguenth at gcc dot gnu.org 2023-01-09 11:19 ` cvs-commit at gcc dot gnu.org [this message] 2023-01-09 11:20 ` rguenth at gcc dot gnu.org 2023-04-12 13:30 ` sjames at gcc dot gnu.org 2023-04-12 13:31 ` sjames at gcc dot gnu.org 2023-04-26 6:55 ` rguenth at gcc dot gnu.org 2023-07-04 9:19 ` rguenth at gcc dot gnu.org 2023-07-04 9:19 ` rguenth 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-101912-4-s29J8irA1y@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).