From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.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 21:40:00 -0000 [thread overview]
Message-ID: <m3vd0j3bgr.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201102162125.44378.pedro@codesourcery.com> (Pedro Alves's message of "Wed, 16 Feb 2011 21:25:44 +0000")
>>>>> "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?
>> + ax_const_l (expr, - fs.regs.cfa_offset);
Pedro> No space after `-'.
Thanks, I will fix it.
Tom
next prev parent reply other threads:[~2011-02-16 21:40 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 [this message]
2011-02-16 23:27 ` Pedro Alves
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=m3vd0j3bgr.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pedro@codesourcery.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