From: Daniel Jacobowitz <dan@debian.org>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: David Daney <ddaney@avtrex.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips <linux-mips@linux-mips.org>
Subject: Re: Question about signal syscalls !
Date: Fri, 2 Feb 2007 11:53:56 -0500 [thread overview]
Message-ID: <20070202165356.GA30584@nevyn.them.org> (raw)
In-Reply-To: <cda58cb80702020836t54ab54bam1b83dd7c1dacb4d8@mail.gmail.com>
On Fri, Feb 02, 2007 at 05:36:30PM +0100, Franck Bui-Huu wrote:
> And now I'm starting to think that we don't need to save static regs in
> setup_sigcontext() either...
It's possible not to (iirc at least one arch does that) but please
don't change it now. This is a userland ABI issue; GDB knows that the
registers are saved, and there are slots for them in
sigcontext/ucontext so it would be unexpected if they were not filled
in. Could break things like pth.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-02 16:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 10:43 Question about signal syscalls ! Franck Bui-Huu
2007-02-01 13:57 ` Ralf Baechle
2007-02-01 14:54 ` Franck Bui-Huu
2007-02-01 17:01 ` David Daney
2007-02-02 8:55 ` Franck Bui-Huu
2007-02-02 16:04 ` David Daney
2007-02-02 16:36 ` Franck Bui-Huu
2007-02-02 16:53 ` Daniel Jacobowitz [this message]
2007-02-02 20:03 ` Franck Bui-Huu
2007-02-02 20:18 ` Franck Bui-Huu
2007-02-02 16:56 ` David Daney
2007-02-02 19:58 ` Franck Bui-Huu
2007-02-02 20:41 ` David Daney
2007-02-05 0:55 ` Daniel Jacobowitz
2007-02-05 1:10 ` Ralf Baechle
2007-02-05 2:30 ` Daniel Jacobowitz
2007-02-05 6:00 ` David Daney
2007-02-05 9:17 ` Franck Bui-Huu
2007-02-05 9:08 ` Franck Bui-Huu
2007-02-01 18:10 ` Ralf Baechle
2007-02-02 8:54 ` Franck Bui-Huu
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=20070202165356.GA30584@nevyn.them.org \
--to=dan@debian.org \
--cc=ddaney@avtrex.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=vagabon.xyz@gmail.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