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? What is the commercial value? What do they get for their efforts? Alan On May 27, 2018, 3:45:32 PM, [email protected] wrote: From: [email protected] To: [email protected] Cc: Date: May 27, 2018, 3:45:32 PM Subject: Re: [LINUX-390] z/Linux 32-bit modules >> Hi Joe. You didn’t show the ELF32 ABI which >> is what is being discussed. > Yes I did. Same document covers 32-bit and 64-bit. No it doesn’t. I read the whole thing and it doesn’t discuss ELF32 at all, and it says that pointers are 8 bytes in size, not sometimes 4, sometimes 8. >> assuming the z/Linux 31-bit software is made >> AM-anything, if it isn’t already. > It aint the software. Its the hardware. The hardware > cannot process 32-bit. It can process 31-bit, and 64-bit. My proposal is to run ELF32 binaries in AM64, so the hardware will allow that. It has not been definitively proven that all the 32-bit software involved can cope with being run in AM64, but that is what is required for my design to work. BFN. Paul. ---------------------------------------------------------------------- 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/
---------------------------------------------------------------------- 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/
