public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Kenneth Johansson <kenneth.c.johansson@ericsson.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] how does stack work?
Date: Tue, 27 Jul 2004 19:31:46 +0200	[thread overview]
Message-ID: <41069182.6030704@ericsson.com> (raw)
In-Reply-To: <DA5CB450F843D611823E0002A5D4DB3C02524A70@renexch1.rennes.thmulti.com>

Seingier Fran?ois-Xavier wrote:

>hello,
>I'm trying to understand how the initial stack works on a ppc4xx. According to start.S this is how the layout looks to me:
>      ___________
>     |           |
>     |           |
>     |           |
>     |    gd_t   |
>     |___________|  
>     |     0     |
>     |___________|  
>     |     0     |  
>     |___________|<-+
>     | reset_vec |  |
>SP ->|___________|  |
>     |           |--+
>     |___________|<-+
>     |           |  |
>     |___________|  |
>     |           |--+
>     |___________|
>     |   ...     |
>
>I can't figure out precisely how the last stack frame works:
>- /* clear final stack frame so that	*/
>  /* stack backtraces terminate cleanly	*/
>I'm not sure to understand the "terminate cleanly".
>  
>
Some debug tool that get confused ??

>- why will the reset_vec be used in case of a stack underflow?
>I tried to find an answer in the "PowerPC compiler writer's guide" about the ABI, but I am not even sure gcc uses an AIX or System V implementation...
>  
>
You can not return from the first function but for some unknown reason 
you do that what should happen ?? a reboot is probably as good as anything.

The ABI for  u-boot is eabi
ftp://ftp.funet.fi/pub/mirrors/sourceware.cygnus.com/pub/binutils/ppc-docs/

  reply	other threads:[~2004-07-27 17:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27 14:33 [U-Boot-Users] how does stack work? Seingier François-Xavier
2004-07-27 17:31 ` Kenneth Johansson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-27 14:56 Seingier François-Xavier

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=41069182.6030704@ericsson.com \
    --to=kenneth.c.johansson@ericsson.com \
    --cc=u-boot@lists.denx.de \
    /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