From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22123 invoked by alias); 27 Apr 2012 15:54:06 -0000 Received: (qmail 22113 invoked by uid 22791); 27 Apr 2012 15:54:05 -0000 X-SWARE-Spam-Status: No, hits=-6.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 27 Apr 2012 15:53:52 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q3RFraoI029443 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 27 Apr 2012 11:53:36 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q3RFrYmm002914 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 27 Apr 2012 11:53:35 -0400 From: Tom Tromey To: Jonathan Larmour Cc: gdb-patches@sourceware.org, Ilija Kocho , Terry Guo Subject: Re: [patch] Add support for VFP d16 layout for Cortex-M4 References: <4F902B4E.9070704@eCosCentric.com> <4F91593B.4020309@redhat.com> <4F95FA8C.7000509@eCosCentric.com> <87ipgm70cc.fsf@fleche.redhat.com> <4F99D8A5.8050702@eCosCentric.com> Date: Fri, 27 Apr 2012 15:55:00 -0000 In-Reply-To: <4F99D8A5.8050702@eCosCentric.com> (Jonathan Larmour's message of "Fri, 27 Apr 2012 00:22:13 +0100") Message-ID: <87vckl41dt.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.95 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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: 2012-04/txt/msg01009.txt.bz2 >>>>> "Jifl" == Jonathan Larmour writes: Jifl> I assume you mean having it in the stub in a pre-compressed form; in which Jifl> case yes, that helps[1]. Yeah. Jifl> But if GDB could handle compressed target descriptions, that would Jifl> be useful. Perhaps the stub could use a different $qSupported Jifl> response to indicate its compressed, or perhaps GDB could Jifl> recognise magic numbers at the start of a $qXfer:features:read Jifl> response and pass to zlib. (e.g. gzip is always 0x1f,0x8b). Yeah, I think it would be a reasonable addition. Tom