Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: <Richard.Earnshaw@arm.com>
Cc: <Richard.Earnshaw@arm.com>, <gdb@sources.redhat.com>
Subject: Re: ARM stack alignment on hand called functions
Date: Wed, 20 Nov 2002 10:59:00 -0000	[thread overview]
Message-ID: <19e701c290c6$e22587f0$0202040a@catdog> (raw)
In-Reply-To: <200211201837.gAKIbXv25319@pc960.cambridge.arm.com>

> OK, but with this change the alignment is being done *after* any arguments
> that have to go onto the stack have been pushed.  It should happen
> *before*.  What happens if you have?
>
> struct f { char a; char b; char c;};
>
> struct f g = {1,2,3};
>
> struct f h (int a, int b, int c, int d, int e)
> {
>   g.c = e;
>   return g;
> }
>
> and then call h from within the debugger.  Is g.c set correctly?
>
> My guess is that it won't, because the integer value for e will have been
> pushed onto the stack incorrectly.
>

Looks like you might be right:  When I 'call h(1,2,3,4,5)', I get:

Breakpoint 2, h (a=1, b=2, c=3, d=1280, e=-31946752) at armstack.c:8

Hmm.... Looks like some further investigation is needed.

Kris


  reply	other threads:[~2002-11-20 18:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2002-11-20 11:40             ` Kris Warkentin
2002-11-21  2:58               ` Richard Earnshaw
     [not found] <200211272021.PAA04606@hub.ott.qnx.com>
2002-11-27 13:13 ` Kris Warkentin

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='19e701c290c6$e22587f0$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=Richard.Earnshaw@arm.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