public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eggert at cs dot ucla.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101770] -Wmaybe-uninitialized false alarm with only locals in GNU diffutils Date: Fri, 19 May 2023 21:44:09 +0000 [thread overview] Message-ID: <bug-101770-4-1kJCSMVtNx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101770-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101770 --- Comment #5 from Paul Eggert <eggert at cs dot ucla.edu> --- I can no longer reproduce the bug in bleeding-edge GNU diffutils, so this bug is not so important in its own right - that is, it's merely that GCC 13.1.1 still mishandles w.i.
prev parent reply other threads:[~2023-05-19 21:44 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-03 23:50 [Bug tree-optimization/101770] New: " eggert at cs dot ucla.edu 2021-08-04 6:34 ` [Bug tree-optimization/101770] " rguenth at gcc dot gnu.org 2021-08-05 14:59 ` msebor at gcc dot gnu.org 2022-11-20 5:00 ` law at gcc dot gnu.org 2022-11-28 22:36 ` pinskia at gcc dot gnu.org 2023-05-19 21:16 ` eggert at cs dot ucla.edu 2023-05-19 21:44 ` eggert at cs dot ucla.edu [this message]
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-101770-4-1kJCSMVtNx@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).