This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC][PATCH 0/2] Make sparcv8 work again on cas enabled hardware
- From: David Miller <davem at davemloft dot net>
- To: triegel at redhat dot com
- Cc: andreas at gaisler dot com, libc-alpha at sourceware dot org, adhemerval dot zanella at linaro dot org, carlos at redhat dot com, software at gaisler dot com
- Date: Thu, 03 Nov 2016 13:22:13 -0400 (EDT)
- Subject: Re: [RFC][PATCH 0/2] Make sparcv8 work again on cas enabled hardware
- Authentication-results: sourceware.org; auth=none
- References: <1478125983.7146.733.camel@localhost.localdomain> <20161102.225245.471656475226254205.davem@davemloft.net> <1478187561.7146.742.camel@localhost.localdomain>
From: Torvald Riegel <triegel@redhat.com>
Date: Thu, 03 Nov 2016 16:39:21 +0100
> Is there any difference between the additional CAS on a v8 and the CAS
> on a v9? If there should be none (eg, same instruciton encoding etc.),
> we wouldn't need a runtime check for this, would we?
A quick look at binutils shows that the encoding appears to be the same.
> That depends on whether we want to support sparc HW that does have a
> CAS. It's still not clear to me whether this is a goal, and if it's a
> goal, whether it's a goal for today or for some time in the future.
I think there is value in supporting pure-v8, however painful it may
be.
I personally don't like to see when we drop support for old systems on
the floor just because it's too inconvenient or cumbersome to keep
them working properly.