On Wed, 2020-04-15 at 14:25 +0100, Dave Wade wrote:
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Harold
Grovesteen
Sent: 15 April 2020 14:15
To: [email protected]
Subject: Re: [h390-vm] memset help
On Wed, 2020-04-15 at 13:24 +0100, Steven Fosdick wrote:
I did wonder about the possibility of setting up gcc as a
cross-compiler but that doesn't seem trivial to do.
Steve.
Yes.??I did accomplish this and it is documented with scripts in
the SATK.??It
used GNU as as the assembler for stand alone, aka bare metal,
coding on
Hercules.??After literally years of work on that, it just did not
work well
enough and I changed to a new toolset that is part of the project.
However, the key difference between GCC on VM and other operating
systems supported by Hercules and GCC as used on Linux is the
output
format.??GCC typically generates ELF object module files.??The GCC
on VM
generates mainframe object modules.??Huge difference and a
fundamental
reason this GCC is used with the operating systems that run on
Hercules.
With my pedants' hat on, it actually generates "normal" Assembler
that is assembled by the XF assembler on VM or MVS.
That is why we get "normal" object files which can be loaded with the
VM loader or the OS Linkage Editor.
I have tried feeding the assembler into Assembler G with poor
results.
I haven't tried Assembler H...
.... its pretty easy to produce a GCC that compiles 370 code on
Windows/Linux. After all that¡¯s how I built the first GCCCMS.
Getting all the assembler to CMS to compile it was the fun part..
No, doubt.
Yes, the generated assembler is the path to the object. ?And the object
dictates where the program can run.
BTW, can CMS compile GCC on VM/370? ?There were issues with that on
MVS.
Harold Grovesteen
Dave
