public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@linaro.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
	 gcc-patches@gcc.gnu.org,  patches@linaro.org
Subject: Re: [2/2] Reducing the overhead of dwarf2 location tracking
Date: Fri, 04 Mar 2011 15:48:00 -0000	[thread overview]
Message-ID: <g4oc5qvqdf.fsf@linaro.org> (raw)
In-Reply-To: <20110304151007.GG30899@tyan-ft48-01.lab.bos.redhat.com> (Jakub	Jelinek's message of "Fri, 4 Mar 2011 16:10:08 +0100")

Jakub Jelinek <jakub@redhat.com> writes:
> On Fri, Mar 04, 2011 at 04:00:06PM +0100, Richard Guenther wrote:
>> But then location lists for those variables depend on the function context
>> and cannot be shared for different callers.  Am I missing something?
>
> Sure, they can't be shared between different functions.  If Richard's patch
> does that, it is wrong.

For the record, it isn't supposed to, although maybe it would without the
dwarf2out_abstract_function change you asked for.  I'll test that next
week and resubmit.

Richard

  parent reply	other threads:[~2011-03-04 15:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 13:57 Richard Sandiford
2011-03-04 14:30 ` Richard Guenther
2011-03-04 14:47   ` Richard Sandiford
2011-03-04 14:50   ` Jakub Jelinek
2011-03-04 15:00     ` Richard Guenther
2011-03-04 15:10       ` Jakub Jelinek
2011-03-04 15:15         ` Richard Guenther
2011-03-04 15:48         ` Richard Sandiford [this message]
2011-03-04 15:22 ` Jakub Jelinek
2011-03-05 14:38   ` Richard Sandiford
2011-03-28  9:00     ` Matthias Klose
2011-04-04 10:50     ` Richard Sandiford

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=g4oc5qvqdf.fsf@linaro.org \
    --to=richard.sandiford@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=patches@linaro.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).