public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113069] gimple-ssa-sccopy.cc:143:12: warning: private field 'curr_generation' is not used [-Wunused-private-field] Date: Mon, 18 Dec 2023 17:34:11 +0000 [thread overview] Message-ID: <bug-113069-4-xqt1Sp6sNg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113069-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113069 David Binderman <dcb314 at hotmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkastl at suse dot cz --- Comment #1 from David Binderman <dcb314 at hotmail dot com> --- git blame has this: cd794c39610 (Filip Kastl 2023-12-14 11:29:31 +0100 143) unsigned curr_generation = 0; Adding author for their opinion.
next prev parent reply other threads:[~2023-12-18 17:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-18 16:59 [Bug c/113069] New: " dcb314 at hotmail dot com 2023-12-18 17:34 ` dcb314 at hotmail dot com [this message] 2023-12-19 22:17 ` [Bug tree-optimization/113069] " mpolacek at gcc dot gnu.org 2023-12-19 22:56 ` cvs-commit at gcc dot gnu.org 2023-12-19 22:56 ` mpolacek at gcc dot gnu.org 2023-12-21 14:24 ` fkastl at suse dot cz
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-113069-4-xqt1Sp6sNg@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).