From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Marcus Shawcroft <marcus.shawcroft@arm.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix for PR tdep/15653: Implement SystemTap SDT probe support for AArch64
Date: Tue, 26 Nov 2013 10:13:00 -0000 [thread overview]
Message-ID: <CAFqB+PyBncAeYPG7Kk46YvU+NdU4JSvp-ju7OQ=gXZrvO-ZDFg@mail.gmail.com> (raw)
In-Reply-To: <m3y54cxk3s.fsf@redhat.com>
Hi
On 25 November 2013 21:11, Sergio Durigan Junior <sergiodj@redhat.com> wrote:
> I am not sure I completely understood your comment. Are you criticizing
> the shared asm parser for ARM targets only, or the generic asm parser in
> stap-probe.c? I assume it is the former. And I also fail to see why it
> can be considered coincidental cohesion... The shared parser covers one
> specific ARM assembly syntax, which is pretty similar to both 32- and
> 64-bit ARM.
> Correct me if I'm wrong, but you're actually against the way I've chosen
> to share the code between the targets, right? Or am I missing something
> here. If that's the case, I can try to come up with a simpler/cleaner
> way to share this code... Suggestions are appreciated, of course :-).
Sorry, I was not clear. I think the a64 and a32 parsers should be kept
separate rather than using a common parser for a different, but
similar syntax, thus avoiding the need to pass the flag that
distinguishes the different syntaxes.
Cheers
/Marcus
next prev parent reply other threads:[~2013-11-26 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-24 23:48 Sergio Durigan Junior
2013-11-25 12:18 ` Marcus Shawcroft
2013-11-25 23:55 ` Sergio Durigan Junior
2013-11-26 10:13 ` Marcus Shawcroft [this message]
2013-11-27 17:52 ` Tom Tromey
2013-12-04 23:35 ` Sergio Durigan Junior
2013-11-27 17:32 ` Tom Tromey
2013-12-04 23:33 ` Sergio Durigan Junior
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='CAFqB+PyBncAeYPG7Kk46YvU+NdU4JSvp-ju7OQ=gXZrvO-ZDFg@mail.gmail.com' \
--to=marcus.shawcroft@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=marcus.shawcroft@arm.com \
--cc=sergiodj@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