From: Richard Earnshaw <rearnsha@arm.com>
To: Jerome Guitton <guitton@act-europe.fr>
Cc: gdb-patches@sources.redhat.com, Richard.Earnshaw@arm.com
Subject: Re: [RFA] ARM : prologue scan
Date: Fri, 05 Sep 2003 10:14:00 -0000 [thread overview]
Message-ID: <200309051014.h85AEGl21565@pc960.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Tue, 22 Jul 2003 13:47:09 +0200." <20030722114709.GB3100@act-europe.fr>
>
> I have done some minor corrections on the previous patch, discard it.
> In attachment, the new version. No regression, no fixed.
>
> --
> Jerome.
>
> 2003-07-21 J. Guitton <guitton@gnat.com>
>
> * arm-tdep.c (arm_skip_prologue): Add the handling of "sub ip, sp #n"
> and "add ip, sp #n", as these instructions can be found in a ATPCS
> compliant prologue.
> (arm_scan_prologue): Ditto.
I don't think there are ever any circumstances when a SUB instruction
would be used. To do so would imply that on return we want to leave space
allocated on the stack. However, it doesn't really harm.
Secondly, and this applies only to the ChangeLog entry itself, this entry
sequence is nothing to do with the ATPCS (the A*T*PCS doesn't even
sanction the use of a frame pointer). Supporting nested functions is at
best a gcc extension (at worst it's a gcc hack). Anyway, it's not normal
to put the reason for a change in a CL entry, so just truncate the
sentence to read:
> 2003-07-21 J. Guitton <guitton@gnat.com>
>
> * arm-tdep.c (arm_skip_prologue): Handle "sub ip, sp #n" and
> "add ip, sp #n" in the prologue.
> (arm_scan_prologue): Ditto.
With that change, this is OK.
R.
next prev parent reply other threads:[~2003-09-05 10:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 14:27 Jerome Guitton
2003-07-21 14:31 ` Daniel Jacobowitz
2003-07-21 14:38 ` Jerome Guitton
2003-07-21 14:57 ` Daniel Jacobowitz
2003-07-21 15:20 ` Jerome Guitton
2003-07-21 15:28 ` Daniel Jacobowitz
2003-07-21 15:43 ` Jerome Guitton
2003-07-22 9:48 ` Jerome Guitton
2003-07-22 11:47 ` Jerome Guitton
2003-09-01 15:45 ` Ping: " Jerome Guitton
2003-09-05 10:14 ` Richard Earnshaw [this message]
2003-09-05 15:56 ` Joel Brobecker
2003-09-05 16:03 ` Richard Earnshaw
2003-09-09 10:23 ` Jerome Guitton
2003-09-09 12:49 ` Richard Earnshaw
2003-09-09 12:52 ` Jerome Guitton
2003-09-23 19:03 ` Jerome Guitton
2003-09-25 14:24 ` [commit] " Jerome Guitton
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=200309051014.h85AEGl21565@pc960.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=guitton@act-europe.fr \
/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