[Top] [All Lists]

Re: [PATCH 0/7] Clean up signal code

To: "Ralf Baechle" <>
Subject: Re: [PATCH 0/7] Clean up signal code
From: "Franck Bui-Huu" <>
Date: Tue, 23 Jan 2007 15:54:23 +0100
Domainkey-signature: a=rsa-sha1; c=nofws;; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cZmSrV9wNVPZOmmOi1kkUjBRMoc/EEc4F88UNMdBGX9Odx0R7JyhX/swMG36rU4SqnBx0vPAF2JblqQr8+UQIyp+HsUVqq5c/cGSwQy5F9drdlgGAbJ+V7vWUgXXTnX+oQu6mgeDKwnq+LhrgIQx94Cqppzammi9Ld+I8ePXl5c=
In-reply-to: <>
Original-recipient: rfc822;
References: <> <>
On 1/23/07, Ralf Baechle <> wrote:
No.  All the information in the MIPS c0_status register is priviledged.
Unlike CISC architectures MIPS has no flags such as zero, equal, overflow
or similar in the status register that is nothing that would constitute
part of the thread context.

The one flag one could possibly argument about might be - but
none of the ABIs or tools or application software can make use of it ...


>     (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

OK, for consistency I'll remove the saving in setup_sigcontext32()


<Prev in Thread] Current Thread [Next in Thread>