It's not the complexity of your code that matters, it's the complexity of the 
code in the compiler.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


________________________________________
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of 
Joseph Reichman <reichman...@gmail.com>
Sent: Tuesday, August 27, 2019 11:28 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: S0C4 XL C Compiler

I have question
If you saw my code it wasn’t complicated a call to debug tool a call to DLL


I would imagine this must of happened to some company using XL C


> On Aug 27, 2019, at 11:25 AM, Seymour J Metz <sme...@gmu.edu> wrote:
>
> I've been programming for over half a century, and one thing that I can 
> assure you of is that until you dig into the code you don't have a clue how 
> easy the fix will be. Things that you thought would be trivial turn out to be 
> intractable and things that you thought were difficult turn out to be trivial.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
> ________________________________________
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of 
> Joseph Reichman <reichman...@gmail.com>
> Sent: Monday, August 26, 2019 7:14 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: S0C4 XL C Compiler
>
> 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.
>
> Compile the hello world to make sure it's not a general compiler problem.
>
> Add statements gradually. When it starts abending, that should be the 
> statement causing the problem.
>
> I suspect a header is causing the problem. Maybe something as simple as a 
> macro calling it's self.
>
> Jon.    On Monday, August 26, 2019, 05:48:21 AM PDT, Allan Staller 
> <allan.stal...@hcl.com> wrote:
>
> I would suggest hard coding (at least) a 150M or greater region. This 
> optimizer code is about 120M.
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
> Joseph Reichman
> Sent: Saturday, August 24, 2019 8:40 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: S0C4 XL C Compiler
>
> REGION=0M I Think that's the max
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
> Charles Mills
> Sent: Saturday, August 24, 2019 9:36 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: S0C4 XL C Compiler
>
> Try increasing the region.
>
> Charles
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Joseph Reichman
> Sent: Saturday, August 24, 2019 6:27 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: S0C4 XL C Compiler
>
>
>
> Simple little program cannt  believe it
>
>
>
>    #include <ctest.h>
>
>    #include <ceeedcct.h>
>
>    #include <string.h>
>
>    #include <stdio.h>
>
>    #include <stdlib.h>
>
>    #include <dll.h>
>
>    #pragma map(__ceetest,"CEETEST")
>
>    #pragma linkage(CEETEST,OS_NOSTACK)
>
>      main( int argc, char* argv[])
>
>    {
>
>    typedef int (DLL_FN)(char *)
>
>    dllhandle* dllHandle;
>
>      DLL_FN* fn;
>
>    _VSTRING commands;
>
>              _FEEDBACK fc;
>
>
>      CEETEST(&commands,&fc);
>
>      dllHandle = dllload("SYSADATA");
>
>      fn = (DLL_FN*) (dllqueryfn(dllHandle, "opendata"));
>
>          fn("SYSADATA");
>
>      return;
>
> }
>
>
>
>    CEE3204S The system detected a protection exception (System Completion 
> Code=0C4).
>
>          From entry point dtFuncDeclarator::BeginNestedFunc(sFuncSymbol*)
> at statement 729 at compile unit offset
>
>          +00000510 at entry offset +00000510 at address 21DEB1B8.
>
>
>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> ::DISCLAIMER::
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> The contents of this e-mail and any attachment(s) are confidential and 
> intended for the named recipient(s) only. E-mail transmission is not 
> guaranteed to be secure or error-free as information could be intercepted, 
> corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses 
> in transmission. The e mail and its contents (with or without referred 
> errors) shall therefore not attach any liability on the originator or HCL or 
> its affiliates. Views or opinions, if any, presented in this email are solely 
> those of the author and may not necessarily reflect the views or opinions of 
> HCL or its affiliates. Any form of reproduction, dissemination, copying, 
> disclosure, modification, distribution and / or publication of this message 
> without the prior written consent of authorized representative of HCL is 
> strictly prohibited. If you have received this email in error please delete 
> it and notify the sender immediately. Before opening any email and/or 
> attachments, please check them for viruses and other defects.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to