> > Hi Timothy. > Great questions.
I don't want to use -m64 because that uses the 64-bit registers for everything, but I wish to produce compact modules using only 32-bit registers and pointers. I would think that most ELF32 programs are already able to use the full 4 GiB address space without needing a recompile. malloc() can start returning addresses in the 2 GiB - 4 GiB range. The only fly in the ointment that I know of is if an application program does a negative index expecting that to wrap at 32 bits. It would be good if compilers can be updated to avoid doing that so that programs start becoming naturally capable of running as AM64. I think gcc on z/Linux doesn't have this problem but I'm not certain. Regarding MVS 3.8j, the situation there is different, but ideally applications themselves are AMODE neutral and the same binary just accepts whatever AMODE it was invoked in instead of demanding a particular AMODE. That way the module can run optimally on any environment. 32-bit modules running as AM64 on z/Linux would basically be treating the environment as AM-infinity, which I think is ideal and this should be the model for all architectures. Rather than having a different mode like x64 has. I think z/Arch is fundamentally superior. BFN. Paul. <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> ---------------------------------------------------------------------- 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/
