public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-4557] Remove unused back_threader destructor. Date: Wed, 20 Oct 2021 10:24:50 +0000 (GMT) [thread overview] Message-ID: <20211020102450.37E983858437@sourceware.org> (raw) https://gcc.gnu.org/g:6fca1761a16c68740f875fc487b98b6bde8e9be7 commit r12-4557-g6fca1761a16c68740f875fc487b98b6bde8e9be7 Author: Aldy Hernandez <aldyh@redhat.com> Date: Wed Oct 20 07:15:17 2021 +0200 Remove unused back_threader destructor. Tested on x86-64 Linux. gcc/ChangeLog: * tree-ssa-threadbackward.c (back_threader::~back_threader): Remove. Diff: --- gcc/tree-ssa-threadbackward.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/gcc/tree-ssa-threadbackward.c b/gcc/tree-ssa-threadbackward.c index 96422a1390e..d94e3b962db 100644 --- a/gcc/tree-ssa-threadbackward.c +++ b/gcc/tree-ssa-threadbackward.c @@ -76,7 +76,6 @@ class back_threader { public: back_threader (bool speed_p, bool resolve); - ~back_threader (); void maybe_thread_block (basic_block bb); bool thread_through_all_blocks (bool may_peel_loop_headers); private: @@ -128,10 +127,6 @@ back_threader::back_threader (bool speed_p, bool resolve) m_resolve = resolve; } -back_threader::~back_threader () -{ -} - // Register the current path for jump threading if it's profitable to // do so. //
reply other threads:[~2021-10-20 10:24 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211020102450.37E983858437@sourceware.org \ --to=aldyh@gcc.gnu.org \ --cc=gcc-cvs@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).