From: "Martin Liška" <mliska@suse.cz>
To: David Malcolm <dmalcolm@redhat.com>, gcc-patches@gcc.gnu.org
Cc: Richard Biener <richard.guenther@gmail.com>
Subject: Re: [PATCH] Do not gather mem stats in run_exit_handles (PR middle-end/69919)
Date: Fri, 26 Feb 2016 10:40:00 -0000 [thread overview]
Message-ID: <56D02BAB.8010708@suse.cz> (raw)
In-Reply-To: <1456423366.22710.28.camel@redhat.com>
On 02/25/2016 07:02 PM, David Malcolm wrote:
> Was this tested with "jit" in --enable-languages? I ask because
> toplev::main can be run repeatedly by libgccjit, and it looks like
> nothing can reset after_memory_report. (Though I don't typically build
> with --enable-gather-detailed-mem-stats, and the jit docs don't mention
> it).
Wasn't, however as I've just retested that with jit in --enable-languages it works.
However, you are right that it's not reset anywhere. I will try to come up with
a better solution for GCC 7.
Martin
prev parent reply other threads:[~2016-02-26 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 11:07 Martin Liška
2016-02-25 14:35 ` Richard Biener
2016-02-25 18:02 ` David Malcolm
2016-02-26 10:40 ` Martin Liška [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=56D02BAB.8010708@suse.cz \
--to=mliska@suse.cz \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.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).