Perfect - thanks

Look in the build.sh script on the source code

Do you mind providing a quick build recipe - what flags to configure a cross compiler to i370/cms 

Thks

Amazing! 🍾

Hello.

Today (well actually, yester-yesterday), I ported the i370 target that GCCMVS uses and put it onto the modern GCC codebase.

https://github.com/wxwisiasdf/gcc-i370

I share this because I would think it's useful for those who want to build PDPCLIB/MVS programs and stuff. Right now it can only compile on Linux and it uses HLASM syntax, there might be some bugs I wouldn't have noticed, otherwise everything works as it should.

Adios.
- Jesus

On Wed, May 25, 2022 at 02:46 AM, adriansutherland67 wrote:

Hello Paul and everyone!

It finally happened, my CREXX project can no longer build on CMS as it is
running out of memory. I can't stomach trying to get s/380 working etc. etc.
(at least for the time being).

So I plan to "just" build it as a cross compiler. As I understand it, this is
an early stage of rebuilding GCC anyway, and the compiler emits assembler
files that you assemble on the mainframe. That is all good with me.

A side point is this may get us nearer to updating the GCC on CE/370 (if that
has not already been done?)

So the quick question - what version of GCCCMS should I use - I am assuming
GCC 3.2.3 CMS 9.0 - but what about GCC 3.4.6 CMS 1.0? Was the 3.4.6 series
abandoned (seems a shame)?

Thanks

Adrian

3.4.6 was abandoned due to too many bugs and no-one to fix them

Use 3.2.3

On Wed, May 25, 2022 at 12:21 AM, <vmdave9@gmail.com> wrote:

Hi, Paul.
What I would like to have available is the following:
1) a GCC compiler and library that runs "out-of-the-box" on a modern 31-bit
CMS
2) the ability to write C programs and routines in that environment.
As I mentioned in my note to Dave Wade, we have access to a modern z/VM 7.2
system here, with a lot of neat toys and tools.
Down the road maybe we could look at how hard it would be to support 64-bit
CMS (or zCMS as it is now called), and perhaps changing the C calling
convention to be in line with z/VM calling convention, so C routines could be
called directly from, say, PL/I code.
Just a thought.
Have a safe trip back home, too, Paul.
DJ

I'm not likely to be coming home btw

Gccmvs should already do what you described out of the box

The caveats on the C library remain

Hello Paul and everyone!

It finally happened, my CREXX project can no longer build on CMS as it is running out of memory. I can't stomach trying to get s/380 working etc. etc. (at least for the time being).

So I plan to "just" build it as a cross compiler. As I understand it, this is an early stage of rebuilding GCC anyway, and the compiler emits assembler files that you assemble on the mainframe. That is all good with me.

A side point is this may get us nearer to updating the GCC on CE/370 (if that has not already been done?)

So the quick question - what version of GCCCMS should I use - I am assuming GCC 3.2.3 CMS 9.0 - but what about GCC 3.4.6 CMS 1.0? Was the 3.4.6 series abandoned (seems a shame)?

Thanks 

Adrian 



 

Hi, Paul.
What I would like to have available is the following:
1) a GCC compiler and library that runs "out-of-the-box" on a modern 31-bit CMS
2) the ability to write C programs and routines in that environment.
As I mentioned in my note to Dave Wade, we have access to a modern z/VM 7.2 system here, with a lot of neat toys and tools.
Down the road maybe we could look at how hard it would be to support 64-bit CMS (or zCMS as it is now called), and perhaps changing the C calling convention to be in line with z/VM calling convention, so C routines could be called directly from, say, PL/I code.
Just a thought.
Have a safe trip back home, too, Paul.
DJ

Hello, Dave.
Yes, I am a Dave too!! 
I figured that on one has done it yet....but I would certainly be more than happy to give anyone that is interested in doing this access to my z/VM 7.2 system here. I also have a lot of the neat toys available here, too, such as the z/VM C/C++ V1.3 compiler and library as well as the older C/370 stuff. 
Drop me a note of-list if you are interested in helping this along.
Take care.
DJ

On Tue, May 24, 2022 at 03:01 AM, <vmdave9@gmail.com> wrote:

Hello, all.
First, let me say how impressed I am with the CE of VM/370....very nice work,
all.
Now I can a question....what is the best way to use GCC on the CE to compile
and link a C program that runs in the so-called "S/380" mode. (or even better,
how to do that for S/390, too).
I want to be able to move the code over to run on "real" CMS on a real z15
processor under z/VM 7.2
I am a Texan, so short sentences with small words is best....

Thank you very much.
DJ

I am in the Philippines at the moment without access to my normal environment

CMS 380 is not as advanced as MVS

Do you need more than 16 mb of memory but less than 60 mb?

If so you need the same link that the gcc module itself does

From memory that is in allcms.exec which is in the gccmvs project in sourceforge

If you want more than 60 mb you will need to rebuild the C library

If you want less than 16 mb on 380 and more than 16 mb only on 390 then another C library should be built

Hello, all. 
First, let me say how impressed I am with the CE of VM/370....very nice work, all.
Now I can a question....what is the best way to use GCC on the CE to compile and link a C program that runs in the so-called "S/380" mode. (or even better, how to do that for S/390, too). 
I want to be able to move the code over to run on "real" CMS on a real z15 processor under z/VM 7.2 
I am a Texan, so short sentences with small words is best....
Thank you very much.
DJ

Hi.

As far as I know, my code **is** using Segment Table on the ASCE - so the translation units should just be 3 (st, pt, data), but still it ends up messed?

- Jesus

Hi.

Done that, now how am I supposed to fill the PTE/STE entries?.
I still get addressing exceptions - kind of hard to work with since there is no indication of what is wrong.

- Jesus