From: Yao Qi <yao@codesourcery.com>
To: David Taylor <dtaylor@emc.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] reserve proposed new bytecodes
Date: Thu, 28 Aug 2014 13:09:00 -0000 [thread overview]
Message-ID: <87fvggg3wz.fsf@codesourcery.com> (raw)
In-Reply-To: <524.1409090060@usendtaylorx2l> (David Taylor's message of "Tue, 26 Aug 2014 17:54:20 -0400")
David Taylor <dtaylor@emc.com> writes:
> I'd like to informally reserve the opcodes and define their syntax and
> semantics. Anyone looking to add a new opcode will look at either
> gdb/doc/agentexpr.texi and/or gdb/common/ax.def.
I don't understand why do you have to reserve these opcodes? IMO, these
opcodes should be added when you contribute your work, together with the
implementations. Although it may be possible that some one adds a new
opcode during your development, you still can simply 'rebase' your
opcodes on top of the trunk.
--
Yao (齐尧)
prev parent reply other threads:[~2014-08-28 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 21:54 David Taylor
2014-08-27 2:46 ` Eli Zaretskii
2014-08-27 13:50 ` David Taylor
2014-08-27 14:55 ` Eli Zaretskii
2014-08-28 13:09 ` Yao Qi [this message]
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=87fvggg3wz.fsf@codesourcery.com \
--to=yao@codesourcery.com \
--cc=dtaylor@emc.com \
--cc=gdb-patches@sourceware.org \
/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