开云体育

GCCRES (GCCLIB Res Stub) is rather large

adriansutherland67 All Messages By This Member #363 It is disappointingly large relative to the real library - need to improve this (otherwise why bother!) It is full of stub functions like this one ? ? ? ? ?EXTRN GCCANCHR GETS? ? ?CSECT ? ? ? ? ?USING GETS,R15 ? ? ? ? ?L? ? ?R15,=V(GCCANCHR) get anchor ptr ? ? ? ? ?L? ? ?R15,0(R15)? ? ? ?get the anchor ? ? ? ? ?LA? ? R15,VTGETS(R15) ? ? ? ? ?BR? ? R15? ? ? ? ? ? go there ? ? ? ? ?LTORG ? ? ? ? ?VTABLE ? ? ? ? ?REGEQU ? ? ? ? ?END I don't fully understand it yet. The point is that each stub is a seperate file/member. Two questions are: 1.VTABLE is quite large. Is it being duplicated in each member? Hence the large size of the TXTLIB. If I put more than one function / sub in the same ASSEMBLE would it therefore be smaller? 2. When linking does it only pull in the members used? Or does it pull in everything from the library? Thanks again!
Dave Wade All Messages By This Member #364 开云体育 Adrian, As I said to Rene a while ago, the while point of all of this is to allow REXX to be dynamically loaded into high memory, so it can call other programs that run in the user space without getting over written. Usually CMS loads things at 20000 (hex) so if you generate REXX as a normal module then when you call another program you wipe yourself out. I believe that if your program uses OS storage macros, when an OS program terminates CMS re-initializes the storage so its important that REXX does not use any OS macros either. Dave (btw some small CMS programs load at E000, the transient program area, but REXX won’t fit there, an any way if it then called a program that runs there it would still over write its self) ? toggle quoted message Show quoted text From: [email protected] <[email protected]> On Behalf Of adriansutherland67 Sent: 15 February 2020 17:19 To: [email protected] Subject: [h390-vm] GCCRES (GCCLIB Res Stub) is rather large ? It is disappointingly large relative to the real library - need to improve this (otherwise why bother!) It is full of stub functions like this one ? ? ? ? ?EXTRN GCCANCHR GETS? ? ?CSECT ? ? ? ? ?USING GETS,R15 ? ? ? ? ?L? ? ?R15,=V(GCCANCHR) get anchor ptr ? ? ? ? ?L? ? ?R15,0(R15)? ? ? ?get the anchor ? ? ? ? ?LA? ? R15,VTGETS(R15) ? ? ? ? ?BR? ? R15? ? ? ? ? ? go there ? ? ? ? ?LTORG ? ? ? ? ?VTABLE ? ? ? ? ?REGEQU ? ? ? ? ?END I don't fully understand it yet. The point is that each stub is a seperate file/member. Two questions are: 1.VTABLE is quite large. Is it being duplicated in each member? Hence the large size of the TXTLIB. If I put more than one function / sub in the same ASSEMBLE would it therefore be smaller? 2. When linking does it only pull in the members used? Or does it pull in everything from the library? Thanks again!
adriansutherland67 All Messages By This Member #365 On Sat, Feb 15, 2020 at 05:57 PM, Dave Wade wrote: REXX to be dynamically loaded into high memory, so it can call But does gcclib need to be resident to allow rexx to be resident? And is loaded in high memory the same as resident? I am assuming so ... The solution I am looking at seems very complex and brittle. Seems only to be needed for stdin and stdout. And I am not sure it works (I fear incompatible versions of assembler sources). I will light it up and see how it goes.? Personally my reading of all the code is people are only using the traditional library and not the resident one, however by changing the GCC calling prologue it is doing potentially evil. I am not being critical, we are all volunteers, and I am often wrong. I am just trying to report what I see and be transparent! Please don't anyone take offence :-) Anyway I think I will test it. If it works, my bad, I will try harder. If it does not work I will unwind all the weird stuff and make it a baseline traditional library. I hope this will still work for rexx (perhaps it will be too big to go into high mem?) Then I will implement a resident library. Using a c static variable for stdin etc.
Dave Wade All Messages By This Member #366 Ok. When I say loaded high I mean loaded with RESLIB. In a modern CMS we have relocatable modules and nucxload which loads this as nucleus extensions. RESLIB does much of this but not all.... Dave toggle quoted message Show quoted text On Sat, 15 Feb 2020, 6:32 pm adriansutherland67, <adrian@...> wrote: On Sat, Feb 15, 2020 at 05:57 PM, Dave Wade wrote: REXX to be dynamically loaded into high memory, so it can call But does gcclib need to be resident to allow rexx to be resident? And is loaded in high memory the same as resident? I am assuming so ... The solution I am looking at seems very complex and brittle. Seems only to be needed for stdin and stdout. And I am not sure it works (I fear incompatible versions of assembler sources). I will light it up and see how it goes.? Personally my reading of all the code is people are only using the traditional library and not the resident one, however by changing the GCC calling prologue it is doing potentially evil. I am not being critical, we are all volunteers, and I am often wrong. I am just trying to report what I see and be transparent! Please don't anyone take offence :-) Anyway I think I will test it. If it works, my bad, I will try harder. If it does not work I will unwind all the weird stuff and make it a baseline traditional library. I hope this will still work for rexx (perhaps it will be too big to go into high mem?) Then I will implement a resident library. Using a c static variable for stdin etc.
adriansutherland67 All Messages By This Member #367 Thanks Dave - I have tested it (with hello world only). The traditional library works (GCCLIB), the resident one doesn't. Dave - you mentioned that you had it working on your latest version - have you the source that you built, or did you just take it off the binary tape? I will run the test from the binaries on the tape tomorrow. Cheers Adrian
Dave Wade All Messages By This Member #368 开云体育 Adrian, I think something is wrong with the profiles being used. When I loaded the modified version from Hans (I think its Hans) things worked, but something isn’t and I am travelling so don’t have time to look now. Dave ? toggle quoted message Show quoted text From: [email protected] <[email protected]> On Behalf Of adriansutherland67 Sent: 15 February 2020 19:35 To: [email protected] Subject: Re: [h390-vm] GCCRES (GCCLIB Res Stub) is rather large ? Thanks Dave - I have tested it (with hello world only). The traditional library works (GCCLIB), the resident one doesn't. Dave - you mentioned that you had it working on your latest version - have you the source that you built, or did you just take it off the binary tape? I will run the test from the binaries on the tape tomorrow. Cheers Adrian
adriansutherland67 All Messages By This Member #370 Rereading the code I am a bit clearer. Still think gcccrab is overkill (or perhaps underkill and it should become a facility that things like brexx could use). It allows user process specific variables when using a? shared libres library. Otherwise all programs using the library would share the same global variable. If that makes any sense. (Presumably brexx having shared variables would be a good thing to allow a program like execio to update rexx variables ... but anyway!) The debugging issue is without printf working I can't be sure if the call to a resident function is not working, or just the gcccrab bit meaning stdout is busted. Oh well ... Work continues
Dave Wade All Messages By This Member #371 开云体育 Yes it makes sense. If REXX calls another program using the shared library then won’t it need this? ? Dave ? toggle quoted message Show quoted text From: [email protected] <[email protected]> On Behalf Of adriansutherland67 Sent: 16 February 2020 09:59 To: [email protected] Subject: Re: [h390-vm] GCCRES (GCCLIB Res Stub) is rather large ? Rereading the code I am a bit clearer. Still think gcccrab is overkill (or perhaps underkill and it should become a facility that things like brexx could use). It allows user process specific variables when using a? shared libres library. Otherwise all programs using the library would share the same global variable. If that makes any sense. (Presumably brexx having shared variables would be a good thing to allow a program like execio to update rexx variables ... but anyway!) The debugging issue is without printf working I can't be sure if the call to a resident function is not working, or just the gcccrab bit meaning stdout is busted. Oh well ... Work continues
Peter Coghlan All Messages By This Member #372 Especially in the case of a REXX program that calls another REXX program, the two programs should not end up accessing each others variables. Regards, Peter Coghlan. Date: Sun, 16 Feb 2020 10:07:28 +0000 From: Dave Wade <dave.g4ugm@...> Subject: Re: [h390-vm] GCCRES (GCCLIB Res Stub) is rather large To: [email protected] Yes it makes sense. If REXX calls another program using the shared library then won’t it need this? Dave From: [email protected] <[email protected]> On Behalf Of adriansutherland67 Sent: 16 February 2020 09:59 To: [email protected] Subject: Re: [h390-vm] GCCRES (GCCLIB Res Stub) is rather large Rereading the code I am a bit clearer. Still think gcccrab is overkill (or perhaps underkill and it should become a facility that things like brexx could use). It allows user process specific variables when using a shared libres library. Otherwise all programs using the library would share the same global variable. If that makes any sense. (Presumably brexx having shared variables would be a good thing to allow a program like execio to update rexx variables ... but anyway!) The debugging issue is without printf working I can't be sure if the call to a resident function is not working, or just the gcccrab bit meaning stdout is busted. Oh well ... Work continues
adriansutherland67 All Messages By This Member #373 I am envisaging a kind of stack for rexx context, etc.
adriansutherland67 All Messages By This Member #374 OK - Got my head round it ... and it is working. I think that we should still treat it as beta but it is a massive product, and this version will be a big improvement on the one on the six pack, I think. I have found some test scripts for the STDC library ...?
Dave Wade All Messages By This Member #375 开云体育 The fixed GCCLIB with the fixed pointer is a huge improvement… Dave ? toggle quoted message Show quoted text From: [email protected] <[email protected]> On Behalf Of adriansutherland67 Sent: 16 February 2020 18:12 To: [email protected] Subject: Re: [h390-vm] GCCRES (GCCLIB Res Stub) is rather large ? OK - Got my head round it ... and it is working. I think that we should still treat it as beta but it is a massive product, and this version will be a big improvement on the one on the six pack, I think. I have found some test scripts for the STDC library ...?

Previous Topic Next Topic