From: Tom Tromey <tromey@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: PATCH RFA: libcpp speedup patch: avoid opening nonexistent files
Date: Wed, 02 May 2007 19:13:00 -0000 [thread overview]
Message-ID: <m3ejlz5a4k.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3irfh2vzy.fsf@dhcp-172-18-118-195.corp.google.com>
>>>>> "Ian" == Ian Lance Taylor <iant@google.com> writes:
>> Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:
[...]
>> ... aren't you leaking 'path' here?
Ian> You're right, thanks for pointing that out. I'll fix that up.
This patch is ok with a fix for the leak. Thanks. And thanks, Ralf,
for noticing this.
Tom
prev parent reply other threads:[~2007-05-02 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 23:02 Ian Lance Taylor
2007-01-08 18:46 ` Ralf Wildenhues
2007-01-08 18:51 ` Ian Lance Taylor
2007-05-02 19:13 ` Tom Tromey [this message]
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=m3ejlz5a4k.fsf@fleche.redhat.com \
--to=tromey@redhat.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).