Re: Suspected bug in wait syscall or similar

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 02/04/2020 11:57, Rolf Eike Beer wrote:
>> The only recent change prior the move to assembly was on 2.25 where we had
>> to disable the stack protector.  For 2.31 release, for instance, I used the
>> gcc 7.5.0 since it didn't trigger this issue.
> 
> I recently tried rebuilding 2.29 on Gentoo with 9.2 and things started 
> breaking, may that still be an issue?

Unfortunately it is, I don't why recent version of gcc stated to generated
a stack frame for the sa_restore function on sparc. 

> 
>>> I know that there have been some stability issues with the Linux kernel on
>>> SPARC with older hardware like the UltraSPARC IIIi. The T5120 we have and
>>> newer machines seem to run relatively fine with a 64-bit userland.
>>
>> Not only stability issues, but I noticed that kernel developers had
>> fixed a SysV IPC kernel issue on 32-bits kernels that has been
>> lingering for years.  So I am not sure how well maintained is
>> 32-bit sparc is in general.
> 
> This seems generally be an option, but noone has a clue of LDOM at the moment. 
> You way come to #gentoo-sparc on Freenode if you want to give a helping hand.
> 
>> [1] https://sourceware.org/glibc/wiki/Release/2.31
> 
> That only lists known test failures regarding sparc?
> 
> Eike
> 

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux