From: Daniel Jacobowitz <dan@debian.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Franck Bui-Huu <vagabon.xyz@gmail.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH 0/7] Clean up signal code
Date: Tue, 23 Jan 2007 09:58:48 -0500 [thread overview]
Message-ID: <20070123145848.GA9900@nevyn.them.org> (raw)
In-Reply-To: <20070123143214.GC18083@linux-mips.org>
On Tue, Jan 23, 2007 at 02:32:14PM +0000, Ralf Baechle wrote:
> > (b) Status register is saved by setup_sigcontext32() but
> > not restored by restore_sigcontext(). Is it a bug ?
>
> Not really a bug but useless code, yes. We used to save c0_status in the
> dark ages but again, no known code - not even IRIX code - relies on this
> field.
For once not even GDB uses it :-)
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-01-23 14:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 14:18 [PATCH 0/7] Clean up signal code Franck Bui-Huu
2007-01-23 14:18 ` [PATCH 1/7] signals: reduce {setup,restore}_sigcontext sizes Franck Bui-Huu
2007-01-23 14:38 ` Ralf Baechle
2007-01-23 16:26 ` Franck Bui-Huu
2007-01-23 16:36 ` Ralf Baechle
2007-01-24 12:25 ` Franck Bui-Huu
2007-01-23 14:18 ` [PATCH 2/7] signal: do not inline functions in signal-common.h Franck Bui-Huu
2007-01-23 14:18 ` [PATCH 3/7] signal: clean up sigframe structure Franck Bui-Huu
2007-01-23 14:35 ` Ralf Baechle
2007-01-23 15:00 ` Franck Bui-Huu
2007-01-23 17:17 ` Ralf Baechle
2007-01-23 14:18 ` [PATCH 4/7] signal32: remove code duplication Franck Bui-Huu
2007-01-23 14:18 ` [PATCH 5/7] signal: test return value of install_sigtramp() Franck Bui-Huu
2007-01-23 14:18 ` [PATCH 6/7] signal: factorize debug code Franck Bui-Huu
2007-01-23 14:18 ` [PATCH 7/7] signal32: reduce {setup,restore}_sigcontext32 sizes Franck Bui-Huu
2007-01-23 14:32 ` [PATCH 0/7] Clean up signal code Ralf Baechle
2007-01-23 14:54 ` Franck Bui-Huu
2007-01-23 14:58 ` Daniel Jacobowitz [this message]
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=20070123145848.GA9900@nevyn.them.org \
--to=dan@debian.org \
--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