On 2018-05-28 08:15, Paul Edwards wrote:
And that, Paul, is why it’s not going to fly.
All of the 31 bit code would have to be reimplemented.
A bunch of other people do all that work and
take on all the risk to what end?
Hi Alan.
What code needs to be reimplemented? I think
it is very unlikely any C code needs to be changed.
A C programmer would need to go to a lot of
effort to make their code 31-bit specific. It is
more likely that it is already AM-anything.
The existing 31-bit code merely needs to be run
as AM64 and it will likely work fine.
https://github.com/torvalds/linux/blob/master/arch/s390/include/asm/compat.h#L201
https://github.com/torvalds/linux/blob/master/arch/s390/include/asm/processor.h#L103
And that's only two from a quick search. You could do some due diligence
in researching it, I guess. People continue to tell you that it won't
work because the kernel assumes either 31bit or 64bit ABI. You call for
a new ABI like x32. Which is fine, but then you need to do all the work
to make that work, for dubious benefits.
What is the commercial value? What do they
get for their efforts?
A decent platform that runs 32 bit binaries with
a 4 GiB address space, and 64 bit binaries with
a 16 EiB address space, just like all competing
platforms provide.
x32 never took off either. And just because a platform provides it for
compatibility doesn't mean it makes sense in today's times.
Kind regards
Philipp Kern
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
