From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7758 invoked by alias); 18 Jan 2008 16:38:30 -0000 Received: (qmail 7748 invoked by uid 22791); 18 Jan 2008 16:38:29 -0000 X-Spam-Check-By: sourceware.org Received: from igw1.br.ibm.com (HELO igw1.br.ibm.com) (32.104.18.24) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 18 Jan 2008 16:38:08 +0000 Received: from mailhub3.br.ibm.com (mailhub3 [9.18.232.110]) by igw1.br.ibm.com (Postfix) with ESMTP id 2031732C44E for ; Fri, 18 Jan 2008 14:16:52 -0200 (BRDT) Received: from d24av01.br.ibm.com (d24av01.br.ibm.com [9.18.232.46]) by mailhub3.br.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id m0IGc5F24419782 for ; Fri, 18 Jan 2008 14:38:05 -0200 Received: from d24av01.br.ibm.com (loopback [127.0.0.1]) by d24av01.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m0IGc4o2029026 for ; Fri, 18 Jan 2008 14:38:05 -0200 Received: from [9.18.238.70] (dyn531803.br.ibm.com [9.18.238.70] (may be forged)) by d24av01.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m0IGc4wg029023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Jan 2008 14:38:04 -0200 Subject: Re: Printing decimal128 types out of registers From: Luis Machado Reply-To: luisgpm@linux.vnet.ibm.com To: Mark Kettenis Cc: bauerman@br.ibm.com, gdb-patches@sourceware.org In-Reply-To: <200801181610.m0IGAhmu002305@brahms.sibelius.xs4all.nl> References: <1194460412.6686.34.camel@localhost> <1200596592.27321.20.camel@gargoyle> <1200598580.32125.11.camel@localhost.localdomain> <1200670954.10815.1.camel@gargoyle> <200801181610.m0IGAhmu002305@brahms.sibelius.xs4all.nl> Content-Type: text/plain Date: Fri, 18 Jan 2008 16:38:00 -0000 Message-Id: <1200674282.10815.10.camel@gargoyle> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 X-SW-Source: 2008-01/txt/msg00477.txt.bz2 > Sorry for not noticing earlier, but why do we need target description > feature for *pseudo* registers? > The purpose of this feature in the target description is to tell GDB which targets support these pseudo-registers, so we're sure that they won't appear on other ppc32 targets that do not support it. This seemed to be a more natural way of doing this, instead of filling the code with target-related conditionals. Regards, -- Luis Machado Software Engineer IBM Linux Technology Center