Re: [Oorexx-devel] OpenSUSE Tumbleweed rexx.img build failure with optimized compile

It might be useful to compare the code generated by the non-optimized version to the optimized code. It might also be useful to compare the optimized code from a earlier compiler version. Rick On Sun, Jul 10, 2016 at 3:38 PM, Erich Steinböck wrote: > I've wrapped

Re: [Oorexx-devel] Using a dynamically assigned port number

That's funny, because earlier someone said that it did. Sent by Magic! > On Jul 10, 2016, at 12:42 PM, Rick McGuire wrote: > > > ooRexx already does not allow Rexx queue communication between different > uids. > > Rick

Re: [Oorexx-devel] OpenSUSE Tumbleweed rexx.img build failure with optimized compile

I've wrapped MemorySegmentPool::newSegment with #pragma GCC push_options #pragma GCC optimize ("O0") .. #pragma GCC pop_options .. but still getting the exception. The code now looks like following, with the failing instruction *very *early in the function body - not sure what that could mean.

Re: [Oorexx-devel] Using a dynamically assigned port number

I still have concerns about this, and please don't take this as vote against, it isn't. In my last email I specifically mentioned the Windows implementation. I still haven't seen any mention on how we are going to make Windows work the same way as *NIX. We all know the saying Rexx Anywhere,

Re: [Oorexx-devel] OpenSUSE Tumbleweed rexx.img build failure with optimized compile

Indeed. I spent quite a few hours on this yesterday and today but I forgot to report back. @Rick, thanks for the suggestions; I am also of the opinion that it is an optimizer bug. If I move the code around, it always chokes on the mov 0x8(%rbp),%rax instruction. Googling for that, I hit

Re: [Oorexx-devel] OpenSUSE Tumbleweed rexx.img build failure with optimized compile

With this patch applied .. --- interpreter/platform/unix/MemorySupport.cpp (revision 11101) +++ interpreter/platform/unix/MemorySupport.cpp (working copy) @@ -216,16 +216,9 @@ else/* uncommitted not enough need a new pool */ { MemorySegmentPool