From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>, Tom Tromey <tromey@redhat.com>
Subject: Re: PR gdb/856
Date: Mon, 29 Sep 2008 17:12:00 -0000 [thread overview]
Message-ID: <200809291811.39619.pedro@codesourcery.com> (raw)
In-Reply-To: <20080929165712.GA3811@adacore.com>
On Monday 29 September 2008 17:57:12, Joel Brobecker wrote:
> :REVIEWMAIL:
>
> > The PR suggests that parse_exp_1 ought to take a sal instead, so this
> > is what I've implemented. I changed any caller with access to a
> > relevant sal or PC to use that; otherwise I changed the code to use
> > either a sal constructed from the block's location, or an empty sal.
>
> I am not sure about changing the block argument into a sal, and would
> argue that changing it into a PC would be slightly better. Indeed,
> apart from the macro-scoping that uses a SAL, all the parse routines
> only really need a PC. Using a SAL would force some of the callers
> that don't already have one at hand to compute it.
>
> A nice corolary is that it would simplify your patch quite a bit
> by getting rid of the need to: replace expression_context_pc by
> expression_context_sal; and define a new function empty_sal.
>
> Thoughts? Andrew Cagney and Jim Blandy both thought using a SAL
> would be a good idea, so the SAL idea does have some weight, but...
>
Hmmm, this rings a bell about a patch I had forgotten:
http://sourceware.org/ml/gdb-patches/2008-05/msg00146.html
Daniel's answer is here, but I never got back to it:
http://sourceware.org/ml/gdb-patches/2008-06/msg00036.html
Just pointing it out to perhaps save someone some time. I haven't
looked at Tom's patch. :-/
--
Pedro Alves
next prev parent reply other threads:[~2008-09-29 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 16:58 Tom Tromey
2008-09-29 16:57 ` Joel Brobecker
2008-09-29 17:12 ` Pedro Alves [this message]
2008-09-29 17:18 ` Joel Brobecker
2008-09-29 18:03 ` Daniel Jacobowitz
2008-09-30 0:13 ` Joel Brobecker
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=200809291811.39619.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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