From: Ian Lance Taylor <iant@google.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org, rdsandiford@googlemail.com
Subject: Re: [PATCH] Slight emit_note_insn_var_location optimization (was Re: Fix mode checks in var-tracking.c)
Date: Wed, 28 Oct 2009 14:22:00 -0000 [thread overview]
Message-ID: <mcrfx93hakm.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <20091023212529.GX14664@tyan-ft48-01.lab.bos.redhat.com> (Jakub Jelinek's message of "Fri\, 23 Oct 2009 23\:25\:29 +0200")
Jakub Jelinek <jakub@redhat.com> writes:
> 2009-10-23 Jakub Jelinek <jakub@redhat.com>
>
> * var-tracking.c (emit_note_insn_var_location): Don't call the second
> vt_expand_loc unnecessarily when location is not a register nor
> memory.
This is OK.
Thanks.
Ian
next prev parent reply other threads:[~2009-10-28 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 21:40 Fix mode checks in var-tracking.c Richard Sandiford
2009-10-22 21:45 ` Jakub Jelinek
2009-10-22 22:31 ` Richard Sandiford
2009-10-23 0:37 ` Jakub Jelinek
2009-10-23 21:28 ` [PATCH] Slight emit_note_insn_var_location optimization (was Re: Fix mode checks in var-tracking.c) Jakub Jelinek
2009-10-28 14:22 ` Ian Lance Taylor [this message]
2009-10-28 14:17 ` Fix mode checks in var-tracking.c Ian Lance Taylor
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=mcrfx93hakm.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rdsandiford@googlemail.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).