From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Daniel Jacobowitz <dan@debian.org>,
Brian Foster <brian.foster@innova-card.com>,
"Maciej W. Rozycki" <macro@codesourcery.com>,
linux-mips@linux-mips.org, libc-ports@sourceware.org,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [PATCH, RFC] MIPS: Implement the getcontext API
Date: Thu, 2 Apr 2009 15:29:36 +0200 [thread overview]
Message-ID: <20090402132936.GB15021@linux-mips.org> (raw)
In-Reply-To: <49AEAE1D.5030205@caviumnetworks.com>
On Wed, Mar 04, 2009 at 08:36:45AM -0800, David Daney wrote:
>> That won't quite retain the ABI: you need to make sure everyone
>> locates it by using the stack pointer instead of the return pc.
>> Fortunately, GCC uses the return PC only for instruction matching
>> today. I have a vague memory it used to use the stack pointer but
>> this was more reliable.
>
> That is correct. Due to various errata the trampoline cannot always be
> at a fixed offset to the signal context bits. So we had to use the
> return PC as you indicate.
To maintaine compatibility with old debuggers and possibly other software
that knows about the stackframe layout I wrote the signal code to only
use the larger alignment of the stackframe if a particular processor
requires it.
However one possible improvment would be to change the way a struct sigframe
or rt_sigframe is allocated on the stack such that not the beginning of
the structure is aligned but the rs_code field is kept aligned. Would
such a change cause problems for gdb?
Ralf
next prev parent reply other threads:[~2009-04-02 13:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 0:12 [PATCH, RFC] MIPS: Implement the getcontext API Maciej W. Rozycki
2009-03-03 16:56 ` David Daney
2009-03-04 8:19 ` Brian Foster
2009-03-04 12:17 ` Daniel Jacobowitz
2009-03-04 16:36 ` David Daney
2009-04-02 13:29 ` Ralf Baechle [this message]
2009-04-02 20:06 ` Daniel Jacobowitz
2009-03-04 15:44 ` Ralf Baechle
2009-03-04 22:25 ` David VomLehn (dvomlehn)
2009-03-04 22:25 ` David VomLehn (dvomlehn)
2009-03-04 22:34 ` David Daney
2009-03-05 7:58 ` MIPS RI/XI & trampolines [was:- [PATCH, RFC] MIPS: Implement the getcontext API ] Brian Foster
2009-03-05 17:01 ` David Daney
2009-04-02 13:38 ` [PATCH, RFC] MIPS: Implement the getcontext API Ralf Baechle
2009-04-16 3:46 ` Markus Gothe
2009-04-17 5:53 ` Ralf Baechle
2009-03-05 15:34 ` Maciej W. Rozycki
2009-03-05 16:58 ` David Daney
2009-03-05 18:23 ` David VomLehn (dvomlehn)
2009-03-05 18:23 ` David VomLehn (dvomlehn)
2009-03-05 21:36 ` Ralf Baechle
2009-03-05 21:39 ` Roland McGrath
2009-03-05 21:53 ` Joseph S. Myers
2009-03-05 22:08 ` David VomLehn (dvomlehn)
2009-03-05 22:08 ` David VomLehn (dvomlehn)
2009-04-02 13:19 ` Ralf Baechle
2009-04-15 20:19 ` Joseph S. Myers
2009-04-15 21:37 ` David Daney
2009-04-18 12:38 ` Ralf Baechle
2009-04-18 17:32 ` Joseph S. Myers
2009-04-20 19:57 ` Maciej W. Rozycki
2009-04-28 19:17 ` Aurelien Jarno
2009-04-28 19:21 ` Philippe Vachon
2009-04-28 20:19 ` Maciej W. Rozycki
2009-04-28 20:53 ` Aurelien Jarno
2009-04-28 21:47 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2009-04-05 18:57 Graziano Sorbaioli
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=20090402132936.GB15021@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=brian.foster@innova-card.com \
--cc=dan@debian.org \
--cc=ddaney@caviumnetworks.com \
--cc=libc-ports@sourceware.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@codesourcery.com \
--cc=macro@linux-mips.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.