public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fkastl at suse dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113054] [14 regressions] ODR warnings when building new SCCP pass
Date: Thu, 21 Dec 2023 18:03:50 +0000 [thread overview]
Message-ID: <bug-113054-4-s8udF3xSKe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113054-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113054
--- Comment #7 from Filip Kastl <fkastl at suse dot cz> ---
Thanks for the fix! Will be careful not to trigger ODR with my future patches.
(In reply to Andrew Pinski from comment #2)
> Note I also don't like how dead_stmts is a static variable either but that
> would be for another change.
How should I get rid of the static variable? Maybe wrap the copy propagation
algorithm in a class as I wrapped the SCC finding algorithm?
next prev parent reply other threads:[~2023-12-21 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 2:09 [Bug tree-optimization/113054] New: " sjames at gcc dot gnu.org
2023-12-18 2:15 ` [Bug tree-optimization/113054] " pinskia at gcc dot gnu.org
2023-12-18 5:05 ` pinskia at gcc dot gnu.org
2023-12-18 5:08 ` pinskia at gcc dot gnu.org
2023-12-18 5:09 ` pinskia at gcc dot gnu.org
2023-12-18 16:36 ` cvs-commit at gcc dot gnu.org
2023-12-18 16:36 ` pinskia at gcc dot gnu.org
2023-12-21 18:03 ` fkastl at suse dot cz [this message]
2023-12-21 18:28 ` pinskia at gcc dot gnu.org
2023-12-21 18:33 ` 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-113054-4-s8udF3xSKe@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).