From: Richard Guenther <richard.guenther@gmail.com>
To: piervit@pvittet.com
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] comment precising need to use free_dominance_info
Date: Thu, 12 May 2011 11:32:00 -0000 [thread overview]
Message-ID: <BANLkTikcV9YohVC2rgLcLdCBgb6DQd_Mxg@mail.gmail.com> (raw)
In-Reply-To: <9551d240d1b3eb591ad5c2ceb8999939@localhost>
On Thu, May 12, 2011 at 12:14 AM, <piervit@pvittet.com> wrote:
> 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.
The patch is not correct. Keeping dom info live is ok.
Richard.
>
> ChangeLog:
> 2011-05-11 Pierre Vittet <piervit@pvittet.com>
>
> * cfgloop.c (flow_loops_find): Add comment remembering to call
> free_dominance_info
>
next prev parent reply other threads:[~2011-05-12 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 6:55 piervit
2011-05-12 11:32 ` Richard Guenther [this message]
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=BANLkTikcV9YohVC2rgLcLdCBgb6DQd_Mxg@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=piervit@pvittet.com \
/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).