public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: <piervit@pvittet.com>
To: <gcc-patches@gcc.gnu.org>
Subject: [PATCH] comment precising need to use free_dominance_info
Date: Thu, 12 May 2011 06:55:00 -0000	[thread overview]
Message-ID: <9551d240d1b3eb591ad5c2ceb8999939@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 397 bytes --]

After using function flow_loops_find in cfgloop.c, it is needed to use 
free_dominance_info to clear structure which have beend added by the 
use of calculate_dominance_info.

I have added a comment precising this.

My contributor number is 634276.


ChangeLog:
2011-05-11  Pierre Vittet  <piervit@pvittet.com>

	* cfgloop.c (flow_loops_find): Add comment remembering to call
	free_dominance_info

[-- Attachment #2: comment_flow_loops_find.diff --]
[-- Type: text/plain, Size: 610 bytes --]

Index: gcc/cfgloop.c
===================================================================
--- gcc/cfgloop.c	(revision 173677)
+++ gcc/cfgloop.c	(working copy)
@@ -368,6 +368,11 @@ init_loops_structure (struct loops *loops, unsigne
 
 /* Find all the natural loops in the function and save in LOOPS structure and
    recalculate loop_depth information in basic block structures.
+
+   This function calls calculate_dominance_info which allocates a structure to
+   handle dominance. It must be freed after use with the function
+   free_dominance_info.
+
    Return the number of natural loops found.  */
 
 int

             reply	other threads:[~2011-05-11 22:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12  6:55 piervit [this message]
2011-05-12 11:32 ` Richard Guenther
2011-05-17 16:33   ` Pierre Vittet

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=9551d240d1b3eb591ad5c2ceb8999939@localhost \
    --to=piervit@pvittet.com \
    --cc=gcc-patches@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).