Remove sparcv8 support

[Andreas Larsson]

On 2016-10-20 21:47, Adhemerval Zanella wrote:
> The sparcv8 build is broken since GLIBC 2.23 due the new pthread
> barrier implementation [1] and since then there is no thread or
> interest on fixing it (Torvald has suggested some options on
> 2.23 release thread).  It won't help with both new pthread rdlock
> and cond implementation, although I would expect that it relies
> on same atomic primitive that was not present for pthread barrier.
>
> AFAIK, recent commercial sparc chips from Oracle all supports
> sparcv9.  The only somewhat recent sparc chip with just sparcv8
> support is LEON4, which I really doubt it cares for glibc support.

Hi!

We do care about GLIBC support for many different LEON3 and LEON4 
systems. GLIBC support for sparcv8 is important for us and it is 
important for our customers. Both LEON3 and LEON4 are continuously used 
in new hardware designs.

We are not always using the latest version of GLIBC (the latest step we 
took was to GLIBC 2.20), so unfortunately we missed this issue. We will 
look into what the extent of the missing support is. Any pointers are 
most welcome.

Do you have a link to the suggested options on the 2.23 release thread? 
I dug around a bit in the archives, but did not find it.

(As a side note, most of the recent LEON3 and LEON4 chips have CAS 
instruction support, but pure sparcv8 support is of course the baseline.)

Best regards,

Andreas Larsson
Software Engineer
Cobham Gaisler