Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: FYI: handle DW_OP_call_frame_cfa in AX compiler
Date: Wed, 16 Feb 2011 23:27:00 -0000	[thread overview]
Message-ID: <201102162224.45388.pedro@codesourcery.com> (raw)
In-Reply-To: <m3vd0j3bgr.fsf@fleche.redhat.com>

On Wednesday 16 February 2011 21:40:04, Tom Tromey wrote:
> >>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
> 
> Pedro> OOC, why the dwarf2_compile_ftype abstraction?  Are you working
> Pedro> on other changes where you'll pass down something else?
> 
> Nope, I just didn't want to make compile_dwarf_to_ax public.
> Maybe it is better to just do that.
> What do you think?

IMO, that'd be better.  Stops everyone else reading the code
from asking that same question in their minds.  :-)

-- 
Pedro Alves


  reply	other threads:[~2011-02-16 22:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 14:35 [unavailable values part 1, 16/17] don't merge almost but not quite adjacent memory ranges to collect Pedro Alves
2011-02-14 12:01 ` Jan Kratochvil
2011-02-16 13:10   ` Pedro Alves
2011-02-16 18:00     ` Tom Tromey
2011-02-16 18:03       ` Pedro Alves
2011-02-16 18:07         ` Tom Tromey
2011-02-16 18:09           ` Pedro Alves
2011-02-16 18:09       ` Tom Tromey
2011-02-16 21:01         ` FYI: handle DW_OP_call_frame_cfa in AX compiler (Was: [unavailable values part 1, 16/17] don't merge almost but not quite adjacent memory ranges to collect) Tom Tromey
2011-02-16 21:31           ` FYI: handle DW_OP_call_frame_cfa in AX compiler Pedro Alves
2011-02-16 21:40             ` Tom Tromey
2011-02-16 23:27               ` Pedro Alves [this message]
2011-02-17 16:24                 ` Tom Tromey

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=201102162224.45388.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --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