public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Filip Kastl <pheeck@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/pheeck/heads/sccp)] removed a TODO comment
Date: Thu,  2 Mar 2023 12:13:41 +0000 (GMT)	[thread overview]
Message-ID: <20230302121341.0CEA23858426@sourceware.org> (raw)

https://gcc.gnu.org/g:6edfe8b07dea30373242d8967db92f94552298b3

commit 6edfe8b07dea30373242d8967db92f94552298b3
Author: Filip Kastl <filip.kastl@gmail.com>
Date:   Thu Mar 2 13:13:02 2023 +0100

    removed a TODO comment

Diff:
---
 gcc/sccp.cc | 2 --
 1 file changed, 2 deletions(-)

diff --git a/gcc/sccp.cc b/gcc/sccp.cc
index 7ae380c9420..010b4d9877e 100644
--- a/gcc/sccp.cc
+++ b/gcc/sccp.cc
@@ -648,8 +648,6 @@ sccp_propagate (auto_vec<gimple *> &copy_stmts)
   BITMAP_FREE (need_eh_cleanup);
   BITMAP_FREE (need_ab_cleanup);
   stmts_to_fixup.release ();
-  
-  // TODO Should I free the vec? Or is it freed automatically?
 
   /* We want to remove dead MEM PHIs because memory is in FUD SSA and the dead
      PHIs would break the FUD property.  */

                 reply	other threads:[~2023-03-02 12:13 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=20230302121341.0CEA23858426@sourceware.org \
    --to=pheeck@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: 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).