3.4.6 made some revamps to the i370 port (compared to 3.2.3), and I
need to make sure those changes have been digested, and no code
has been lost, so that I can pick up the final i370 port and move it.
But there were probably also (mechanical) changes to the port between when
3.4 branched (long before 3.4.6 was released) and when the port was
removed from trunk - that's why the last revision before it was removed
from trunk may be a better starting point.
Ok, I understand now. So there were some changes, that would
nominally have made it to GCC 4, but were in fact never officially
released, because it was dropped before release.
So, prior to starting a GCC 4 port (ie the changes may not be
desirable for the GCC 3.4.6 port I am currently working on), I
need to get GCC 3.4 as a base, GCC 3.4.6 as one derivative,
and SVN 77215, then do a 3-way diff/merge to obtain the
"nominal GCC 4" changes.
Or perhaps not.
I don't want the 3.4.6 changes at that point, since anything of
value will be covered by SVN 77215. So I need to use GCC 3.4.6
as the base, my personal version as one derivative, SVN 77215
as the second derivative, and feed that into the 3-way diff.
Ok, I'll do that when I'm in a position to do the GCC 4 port
attempt. I'm still months away from completing the GCC 3.4.6
port, and there are other MVS-related projects that are more
important than what is basically a transparent 3.2.3 to 4
upgrade that will only start being useful when it enables something
else to happen (such as the PL/1 front-end).
So I'll be working on that stable 3.4.6 before taking my chances
with what is basically an axed beta (SVN 77215), with still no
indication of whether even a perfectly working self-compiling
i370 target will be accepted unless the testsuite is working first
(and even if it was working, that still may not be enough - as
the next hoop may be an s390 merge - and a requirement to
switch from 370 to 390).
BFN. Paul.
