From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8406 invoked by alias); 28 Aug 2014 13:09:51 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 8368 invoked by uid 89); 28 Aug 2014 13:09:51 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 28 Aug 2014 13:09:49 +0000 Received: from svr-orw-fem-06.mgc.mentorg.com ([147.34.97.120]) by relay1.mentorg.com with esmtp id 1XMzSU-0006Mw-7C from Yao_Qi@mentor.com ; Thu, 28 Aug 2014 06:09:46 -0700 Received: from GreenOnly (147.34.91.1) by SVR-ORW-FEM-06.mgc.mentorg.com (147.34.97.120) with Microsoft SMTP Server id 14.2.247.3; Thu, 28 Aug 2014 06:09:45 -0700 From: Yao Qi To: David Taylor CC: "gdb-patches@sourceware.org" Subject: Re: [PATCH] reserve proposed new bytecodes References: <524.1409090060@usendtaylorx2l> Date: Thu, 28 Aug 2014 13:09:00 -0000 In-Reply-To: <524.1409090060@usendtaylorx2l> (David Taylor's message of "Tue, 26 Aug 2014 17:54:20 -0400") Message-ID: <87fvggg3wz.fsf@codesourcery.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2014-08/txt/msg00605.txt.bz2 David Taylor 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. --=20 Yao (=E9=BD=90=E5=B0=A7)