Linux MIPS Architecture development
 help / color / mirror / Atom feed
* siginfo difference MIPS and other arches
@ 2010-10-08 14:16 Manuel Lauss
  2010-10-08 15:53 ` Ralf Baechle
  0 siblings, 1 reply; 4+ messages in thread
From: Manuel Lauss @ 2010-10-08 14:16 UTC (permalink / raw)
  To: Linux-MIPS

Hello,

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?

Manuel

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: siginfo difference MIPS and other arches
  2010-10-08 14:16 siginfo difference MIPS and other arches Manuel Lauss
@ 2010-10-08 15:53 ` Ralf Baechle
  2010-10-08 15:55   ` Manuel Lauss
  0 siblings, 1 reply; 4+ messages in thread
From: Ralf Baechle @ 2010-10-08 15:53 UTC (permalink / raw)
  To: Manuel Lauss; +Cc: Linux-MIPS

On Fri, Oct 08, 2010 at 04:16:33PM +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.

  Ralf

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: siginfo difference MIPS and other arches
  2010-10-08 15:53 ` Ralf Baechle
@ 2010-10-08 15:55   ` Manuel Lauss
  2010-10-08 15:58     ` Ralf Baechle
  0 siblings, 1 reply; 4+ messages in thread
From: Manuel Lauss @ 2010-10-08 15:55 UTC (permalink / raw)
  To: Ralf Baechle; +Cc: Linux-MIPS

On Fri, Oct 8, 2010 at 5:53 PM, Ralf Baechle <ralf@linux-mips.org> wrote:
> On Fri, Oct 08, 2010 at 04:16:33PM +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? :)  )

Manuel

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: siginfo difference MIPS and other arches
  2010-10-08 15:55   ` Manuel Lauss
@ 2010-10-08 15:58     ` Ralf Baechle
  0 siblings, 0 replies; 4+ messages in thread
From: Ralf Baechle @ 2010-10-08 15:58 UTC (permalink / raw)
  To: Manuel Lauss; +Cc: Linux-MIPS

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2010-10-08 15:58 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-08 14:16 siginfo difference MIPS and other arches Manuel Lauss
2010-10-08 15:53 ` Ralf Baechle
2010-10-08 15:55   ` Manuel Lauss
2010-10-08 15:58     ` Ralf Baechle

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox