The end-of-DSA, could be propagated in a field with the stack mechanism, like the NAB is. i.e. additional fields appended to the save area. Also, Metal C allows for an "environment", which as best I can tell, sets up a heap. But it's optional unless you need a heap (several of the library functions do). It's similar to LE's CAA, rooted on R12.
sas On Wed, Dec 7, 2016 at 9:37 AM, Tom Marchant < [email protected]> wrote: > On Wed, 7 Dec 2016 08:56:08 -0500, Steve Smith wrote: > > >I meant that as a general statement; it would need to be implemented by > the > >Metal C compiler. > > I understood that. There is still the problem of where to store the > information > so that it can be checked. Does Metal C have any global data areas that > are available to all routines? > > >On Tue, Dec 6, 2016 at 5:15 PM, Tom Marchant < > >[email protected]> wrote: > > > >> On Tue, 6 Dec 2016 16:26:24 -0500, Steve Smith wrote: > >> > >> >However, it's really very simple to add a stack-overflow check to entry > >> >logic > >> > >> Yes, if you have the address of the end of the "stack". AFAICT, there > >> is no place to store that information for each routine to check it. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- sas ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
