From: "Weddington, Eric" <Eric.Weddington@atmel.com>
To: "Petr Hluzín" <petr.hluzin@gmail.com>, gdb@sourceware.org
Cc: "Tristan Gingold" <gingold@adacore.com>,
"Joerg Wunsch" <joerg_wunsch@uriah.heep.sax.de>
Subject: RE: a review and questions on avr_scan_prologue()
Date: Tue, 16 Feb 2010 05:13:00 -0000 [thread overview]
Message-ID: <258DDD1F44B6ED4AAFD4370847CF58D509EB0F24@csomb01.corp.atmel.com> (raw)
In-Reply-To: <6a6f635a1002131556sc428adfu6033489930eca7b6@mail.gmail.com>
> -----Original Message-----
> From: Petr Hluzín [mailto:petr.hluzin@gmail.com]
> Sent: Sunday, February 14, 2010 5:27 AM
> To: gdb@sourceware.org
> Cc: Tristan Gingold
> Subject: a review and questions on avr_scan_prologue()
>
> Hello
>
> 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 put 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. Recently the AVR GCC port generates RTL-based prologues and epiloges. I'm sure AVR GDB has not kept up.
> 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
next prev parent reply other threads:[~2010-02-16 5:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 23:56 Petr Hluzín
2010-02-16 5:13 ` Weddington, Eric [this message]
2010-02-17 9:02 ` Tristan Gingold
2010-02-20 23:20 ` Petr Hluzín
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=258DDD1F44B6ED4AAFD4370847CF58D509EB0F24@csomb01.corp.atmel.com \
--to=eric.weddington@atmel.com \
--cc=gdb@sourceware.org \
--cc=gingold@adacore.com \
--cc=joerg_wunsch@uriah.heep.sax.de \
--cc=petr.hluzin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox