linux-mips
[Top] [All Lists]

Re: siginfo difference MIPS and other arches

To: Manuel Lauss <manuel.lauss@googlemail.com>
Subject: Re: siginfo difference MIPS and other arches
From: Ralf Baechle <ralf@linux-mips.org>
Date: Fri, 8 Oct 2010 16:58:23 +0100
Cc: Linux-MIPS <linux-mips@linux-mips.org>
In-reply-to: <AANLkTimYGDoRovYgbReeBihD2nfYFHE_CmwJjv2_=s7v@mail.gmail.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <AANLkTikXySeekzpYeGf6wuH5NTMxLCK_oirvBcDu4h63@mail.gmail.com> <20101008155319.GC12107@linux-mips.org> <AANLkTimYGDoRovYgbReeBihD2nfYFHE_CmwJjv2_=s7v@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.21 (2010-09-15)
On Fri, Oct 08, 2010 at 05:55:01PM +0200, Manuel Lauss wrote:

> >> current -git build breaks because of upstream commit
> >> a337fdac7a5622d1e6547f4b476c14dfe5a2c892, which introduced
> >> an unconditional check for siginfo_._sifields._sifault._si_addr_lsb field.
> >>
> >> Is there a reason why MIPS doesn't use the default siginfo_t structure
> >> as other architectures do?
> >
> > History - the MIPS structure is identical to IRIX.
> 
> Does anyone still run IRIX binaries on current linux?
> (and Isn't IRIX dead anyway? :)  )

Doesn't matter - you can't change the definition without breaking
binary compatibility.

  Ralf

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