The port is to a pure C90 environment (ie not posix, not unix). It was a
major effort to achieve that, and it has only just been completed to the
point where the compiler recompiles itself with full optimization. The
environment where it runs is not set up to run shell scripts or makes
or test suites. It's set up to run JCL, and there's a stack of JCL card
decks to allow GCC to compile, which would be good to have included
in the i370 directory.
You can test a cross compiler if you have some way of copying a test
executable to the i370 system
It doesn't build executables either.
Only the "-S" option is used.
With that restriction, GCC merely reads a bunch of text files and
writes a text file, and thus is amenable to being a pure C90
application. That's how it manages to work at all.
running it and getting its output and exit
status back (actually you don't need to be able to get the exit status
since DejaGnu has wrappers to include it in the output if needed).
It so happens that MVS/380 has the ability to be run in batch, and
extracting the exit code won't be a problem either.
Note however that I normally do all my GCC work in Windows,
and the batch running etc is done with batch files.
There
is no need for the target to be able to run shell scripts or makes. You
would need to write your own DejaGnu board file that deals with copying
to/from the i370 system and running programs there. The testsuite
routinely runs for much more limited embedded systems (using appropriate
board files).
I have a large backlog of work to do with the i370 port already, starting
with getting gcc 3.4.6 running natively. Isn't that a more productive
thing to do? Even after 3.4.6 is done, so that every scrap of code is
available, then there's version 4 to do!
BFN. Paul.
