From: Richard Guenther <richard.guenther@gmail.com>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: Jakub Jelinek <jakub@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Dump file usage patterns?
Date: Fri, 28 Jan 2011 16:52:00 -0000 [thread overview]
Message-ID: <AANLkTinuQdfWVASSoMOD-=DkiFZ+ZOdGnJDGFMjgd9iH@mail.gmail.com> (raw)
In-Reply-To: <4D42EAEA.6040907@codesourcery.com>
On Fri, Jan 28, 2011 at 5:12 PM, Bernd Schmidt <bernds@codesourcery.com> wrote:
> On 08/25/2010 01:17 PM, Jakub Jelinek wrote:
>> On Wed, Aug 25, 2010 at 12:55:07PM +0200, Bernd Schmidt wrote:
>>> Should we print cselib
>>> information only when given a specific flag - I don't find it very
>>> useful and it clutters up the dump files?
>>
>> For var-tracking issues it is very useful, but I guess I don't mind enabling
>> it with an extra option.
>
> How's this? Bootstrapped and tested on i686-linux.
Looks good to me.
Richard.
>
> Bernd
>
prev parent reply other threads:[~2011-01-28 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 11:12 Bernd Schmidt
2010-08-25 12:22 ` Richard Guenther
2010-08-25 12:50 ` Jakub Jelinek
2011-01-28 16:46 ` Bernd Schmidt
2011-01-28 16:52 ` Richard Guenther [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='AANLkTinuQdfWVASSoMOD-=DkiFZ+ZOdGnJDGFMjgd9iH@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).