From: "Kris Warkentin" <kewarken@qnx.com>
To: <gdb@sources.redhat.com>
Subject: Re: ARM stack alignment on hand called functions
Date: Wed, 27 Nov 2002 13:13:00 -0000 [thread overview]
Message-ID: <076a01c29659$d7e41520$0202040a@catdog> (raw)
In-Reply-To: <200211272021.PAA04606@hub.ott.qnx.com>
> Forwarded From: Richard Earnshaw <rearnsha@arm.com>
> > > Can I suggest downloading a current GDB snap and find out if the
problem
> > > is still present (and if it isn't, follow through with a patch)?
> > > Otherwize this will slip through the cracks, only to re-bite you (and
> > > others) later :-(
> > >
> > > Andrew
> > >
> > >
> >
> > I can see no evidence that the current code is correct either, so
perhaps
> > we should file a PR with all this info.
> >
> > R.
Sorry about the late reply...I had missed this in purging my email. I used
the arm_push_arguments() : arm-tdep.c from your head branch in isolation and
observed the same problem. When I forced an sp alignment at the top of
arm_push_arguments(), it worked fine. Now I wonder, however, if " sp =
(sp - 3) & ~3 " is too simplistic of a fix? Can we assume that arm will
always have 4 byte alignment? 2) Can we assume that arm stacks will always
grow downward? I'm thinking yes to the direction but no to the alignment so
perhaps we should do a
#define STACK_ALIGN_SIZE 4
in tm-arm.h and then do:
sp = (sp - STACK_ALIGN_SIZE + 1) & ~(STACK_ALIGN_SIZE - 1);
????
Kris
next parent reply other threads:[~2002-11-27 21:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200211272021.PAA04606@hub.ott.qnx.com>
2002-11-27 13:13 ` Kris Warkentin [this message]
2002-11-20 7:29 Kris Warkentin
2002-11-20 7:58 ` Richard Earnshaw
2002-11-20 8:10 ` Kris Warkentin
2002-11-20 8:21 ` Richard Earnshaw
2002-11-20 8:26 ` Kris Warkentin
2002-11-20 9:18 ` Andrew Cagney
2002-11-20 9:35 ` Kris Warkentin
2002-11-26 14:01 ` Andrew Cagney
2002-11-27 1:18 ` Richard Earnshaw
2002-11-20 10:37 ` Richard Earnshaw
2002-11-20 10:59 ` Kris Warkentin
2002-11-20 11:40 ` Kris Warkentin
2002-11-21 2:58 ` Richard Earnshaw
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='076a01c29659$d7e41520$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=gdb@sources.redhat.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