From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6470 invoked by alias); 16 Feb 2010 05:13:29 -0000 Received: (qmail 6457 invoked by uid 22791); 16 Feb 2010 05:13:27 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from newsmtp5.atmel.com (HELO sjogate2.atmel.com) (204.2.163.5) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 16 Feb 2010 05:13:23 +0000 Received: from csomb01.corp.atmel.com ([10.95.30.150]) by sjogate2.atmel.com (8.13.6/8.13.6) with ESMTP id o1G5BBew012843; Mon, 15 Feb 2010 21:11:11 -0800 (PST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: a review and questions on avr_scan_prologue() Date: Tue, 16 Feb 2010 05:13:00 -0000 Message-ID: <258DDD1F44B6ED4AAFD4370847CF58D509EB0F24@csomb01.corp.atmel.com> In-Reply-To: <6a6f635a1002131556sc428adfu6033489930eca7b6@mail.gmail.com> References: <6a6f635a1002131556sc428adfu6033489930eca7b6@mail.gmail.com> From: "Weddington, Eric" To: =?iso-8859-1?Q?Petr_Hluz=EDn?= , Cc: "Tristan Gingold" , "Joerg Wunsch" Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-02/txt/msg00110.txt.bz2 =20 > -----Original Message----- > From: Petr Hluz=EDn [mailto:petr.hluzin@gmail.com]=20 > Sent: Sunday, February 14, 2010 5:27 AM > To: gdb@sourceware.org > Cc: Tristan Gingold > Subject: a review and questions on avr_scan_prologue() >=20 > Hello >=20 > I took a look at avr-tdep.c [1] and I found some places which are > either bug or are not clear to me. Could you please at least fill out bug reports for these 2 issues? Please p= ut me on the CC list. That way they're recorded. > Also: > The avr_scan_prologue()'s recognizes several well-known prologues. Is > there a reason why it does not use the general prologue analysis > algorithm as described in the documentation [2]? IIRC, the AVR GCC prologue and epilogue used to be some fixed code. Recentl= y the AVR GCC port generates RTL-based prologues and epiloges. I'm sure AVR= GDB has not kept up. =20 > I think universal prologue analysis is quite easy with AVR arch. The > code might be shorter (though less clear). > I might try to write the code if you are interested. > (The current prologue scan code chokes on hand-crafted assembly.) Yes, we would be very interested. Eric Weddington