From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8095 invoked by alias); 1 Jul 2014 16:29:43 -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 8073 invoked by uid 89); 1 Jul 2014 16:29:42 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 01 Jul 2014 16:29:39 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s61GTaX3026123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 1 Jul 2014 12:29:37 -0400 Received: from barimba (ovpn-113-95.phx2.redhat.com [10.3.113.95]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s61GTZt6025743 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NO); Tue, 1 Jul 2014 12:29:36 -0400 From: Tom Tromey To: lin zuojian Cc: gdb-patches@sourceware.org Subject: Re: [PATCH] Adding bit position to ptype References: <20140618031308.GA7252@ubuntu> <871tumffwz.fsf@fleche.redhat.com> <20140701093348.GA25342@ubuntu> Date: Tue, 01 Jul 2014 16:29:00 -0000 In-Reply-To: <20140701093348.GA25342@ubuntu> (lin zuojian's message of "Tue, 1 Jul 2014 17:33:48 +0800") Message-ID: <87bnt9rqj4.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2014-07/txt/msg00020.txt.bz2 >>>>> ">" == lin zuojian writes: >> Before posting the second patch, I may make your point clear first. >> Do you want me to add a flag to control this behavior? Yeah, I think the behavior should be optional and should default to "off". I think it's best to consider this as a new feature -- so it would need a new ptype flag, documentation, NEWS entry, and tests. The bad news is that this is much more work for you. That's probably why nobody has implemented it before. Tom