From: Richard Henderson <rth@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Alexandre Oliva <aoliva@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Add --param max-vartrack-reverse-op-size=N (PR debug/54402)
Date: Wed, 02 Jan 2013 23:52:00 -0000 [thread overview]
Message-ID: <50E4BC2C.50508@redhat.com> (raw)
In-Reply-To: <20121213093954.GN2315@tucnak.redhat.com>
On 12/13/2012 01:39 AM, Jakub Jelinek wrote:
> PR debug/54402
> * params.def (PARAM_MAX_VARTRACK_REVERSE_OP_SIZE): New param.
> * var-tracking.c (reverse_op): Don't add reverse ops to
> VALUEs that have already
> PARAM_VALUE (PARAM_MAX_VARTRACK_REVERSE_OP_SIZE) or longer
> locs list.
Ok.
r~
prev parent reply other threads:[~2013-01-02 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 9:40 Jakub Jelinek
2013-01-02 23:52 ` Richard Henderson [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=50E4BC2C.50508@redhat.com \
--to=rth@redhat.com \
--cc=aoliva@redhat.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).