Finding the compile time problem could take some time. If it's a missing ifdef
or looping macro, then it will be an easy fix but more difficult to find
because it will be in an include..
This is a compiler abend. MAIN does not have anything obvious missing to cause
a compiler abend so the problem is most likely in an include. That's why I said
try hello world program.
I seriously doubt you need more than 2GB (AMODE 31 region=0M). Do you really
believe you have an AMODE64 problem? You could try compiling a standard C
debugger with IBM C. I don't believe GCCMVS is amode64 compatible yet but I
could be wrong. Someone is working on it at this time but I would be leary of
his assumptions.
Jon.
On Monday, August 26, 2019, 04:14:54 PM PDT, Joseph Reichman
<reichman...@gmail.com> wrote:
Jon
You are right on I saw those messages from the compiler
I tried to take out a number statements and still got it
I opened a PMR with IBM they said they were able to recreate the problem and
would get back to me wednesday
I would think this would take 5 minutes to fix
I saw some free C compilers E.G. GCCMVS wonder if they have a debugger probably
cannt run AMODE64
-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Jon
Perryman
Sent: Monday, August 26, 2019 7:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: S0C4 XL C Compiler
You never mentioned this this was a compile time abend. I assumed it was a run
time abend.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
