From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31199 invoked by alias); 16 Apr 2012 14:28:05 -0000 Received: (qmail 31189 invoked by uid 22791); 16 Apr 2012 14:28:03 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_40,KHOP_THREADED,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 16 Apr 2012 14:27:35 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id BD7262F78003; Mon, 16 Apr 2012 15:27:33 +0100 (BST) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id REpYBIIbKvcm; Mon, 16 Apr 2012 15:27:32 +0100 (BST) Message-ID: <4F8C2C53.8070306@eCosCentric.com> Date: Mon, 16 Apr 2012 14:40:00 -0000 From: Jonathan Larmour User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Lightning/1.0b3pre Thunderbird/3.1.16 MIME-Version: 1.0 To: Terry Guo CC: gdb-patches@sourceware.org, Joey Ye , Matthew Gretton-Dann Subject: Re: Fwd: Re: [patch] Add support for ARMv7M devices. References: <4F59ED15.1030109@redhat.com> <001c01cd1ba6$44a2bf50$cde83df0$@guo@arm.com> In-Reply-To: <001c01cd1ba6$44a2bf50$cde83df0$@guo@arm.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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/msg00414.txt.bz2 On 16/04/12 08:55, Terry Guo wrote: > > Can somebody please tell me how the "guess" mechanism works? How can the > buf_len in function process_g_packet become correct with "guess"? Have a look at remote_read_description(), which is called early on when connecting to the target. Once the target description (tdesc) is set from there, subsequent calls to process_g_packet() will have an appropriate value for sizeof_g_packet. > Can we just make the arm-with-m.xml always include unnamed FPA registers? So > that it can cope with the case with or without FPA registers. I think that it might have been possible to arrange this if the FPA registers happened to be sent at the very end of the "normal" register set (courtesy of some handling in process_g_packet() of smaller 'g' packets). But i don't think that's possible here given the FPA regs come after the PC but before the XPSR at the end; at least not without adding much more machinery somewhere, including extending the target description syntax. I might be wrong though, as I don't know the ins-and-outs of this code as well as others here. Jifl -- eCosCentric Limited http://www.eCosCentric.com/ The eCos experts Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571 Registered in England and Wales: Reg No 4422071. ** Visit us at NEW:UK - the UK Embedded & Electronics Exhibition ** ** ARM Partner Pavilion/Stand #114. 18-19 April. Birmingham NEC ** ------["Si fractum non sit, noli id reficere"]------ Opinions==mine