From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] auto-generate most target debug methods
Date: Tue, 15 Jul 2014 15:20:00 -0000 [thread overview]
Message-ID: <87a98a1whj.fsf@fleche.redhat.com> (raw)
In-Reply-To: <53C5042B.6080406@redhat.com> (Pedro Alves's message of "Tue, 15 Jul 2014 11:36:27 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> What I'm not sure I like is the need for new typedefs. Seems odd to
Pedro> me to have a textual mismatch between the declaration and all
Pedro> the implementations.
Yeah.
Pedro> Did you try an __attribute__(())-like approach?
I thought of it, but I didn't give it a try, I think just because the
whole idea was speculative enough that I didn't want to sink a lot of
time into it.
Pedro> void (*to_resume) (struct target_ops *, ptid_t, int step,
Pedro> enum gdb_signal)
Pedro> TARGET_DEBUG_PRINT (step, print_target_resume_step)
Pedro> TARGET_DEFAULT_NORETURN (noprocess ());
Syntactically I think I prefer the attributes next to the parameters;
though perhaps this other approach can be used to solve the
debug_print_register problem.
I'll go a bit deeper.
Tom
next prev parent reply other threads:[~2014-07-15 15:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 20:04 Tom Tromey
2014-06-20 8:00 ` Yao Qi
2014-06-20 14:04 ` Tom Tromey
2014-07-15 11:17 ` Pedro Alves
2014-07-15 15:20 ` Tom Tromey [this message]
2014-07-16 15:46 ` Tom Tromey
2014-07-17 14:50 ` Pedro Alves
2014-07-17 16:12 ` Tom Tromey
2014-07-17 16:35 ` Pedro Alves
2014-07-17 16:41 ` Tom Tromey
2014-07-17 16:52 ` Pedro Alves
2014-07-17 16:49 ` Tom Tromey
2014-07-17 16:51 ` Pedro Alves
2014-07-24 13:59 ` 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=87a98a1whj.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).