On 7/12/22 10:53, Joseph Reichman wrote:
David Crayford suggested I use uss pthread wonder if that corresponds to z/os
task
Of course! Although the POSIX semantics are different. pthreads are not
hierarchical and the thread can be detached from the thread that spawned
it. This is
David Crayford suggested I use uss pthread wonder if that corresponds to z/os
task
Going to try and research that
Thanks
> On Dec 6, 2022, at 9:30 PM, David Crayford wrote:
>
> We discussed this with the C/C++ compiler devs when we were beta testing the
> Open XL C/C++ compiler. They
Pthread is Unix system services I assume I can use it in LE with runtime option
posix(on)
> On Dec 6, 2022, at 9:30 PM, David Crayford wrote:
>
> We discussed this with the C/C++ compiler devs when we were beta testing the
> Open XL C/C++ compiler. They said it was on their radar but would
We discussed this with the C/C++ compiler devs when we were beta testing
the Open XL C/C++ compiler. They said it was on their radar but would
need work from the binder team to implement similar plumbing to
writeable static. I got the impression that it won't happen soon. It's a
PITA as it
To my limited understanding, there is not currently support for thread-local
storage on z/OS.
An LE enclave does not correspond 1 to 1 to a thread.
I think that "writeable static", for example, is on an enclave basis, not a
thread basis.
I'm sure others know this far better than I.
Peter
In Language Environment threads run under enclaves. Each thread represents an
independent instance of a routine running using enclave's resources.
Memory is allocated by threads and owned by the parent enclave. It exists from
when it is allocated to when it is explicitly freed or to when the
Hi
Is there a concept like this in XL C\C++
I looked at the chapter on DLL's in the XL C\C++ programing guide
And unlike windows there is no DLLMain just a main with functions you can
export and later call by the imported DLL appl
If you do a malloc in the main()
Will that
