➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author David.Edelsohn
Recipients David.Edelsohn, Michael.Felt, lys.nikolaou, pablogsal, skrah
Date 2020-07-06.16:13:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1594052010.85.0.0019685733702.issue41215@roundup.psfhosted.org>
In-reply-to
Content 
I don't believe that this is an XLC bug, but I suspect that it is undefined behavior / implementation-defined behavior.

I suspect that this is tripping over AIX/XLC null behavior. AIX specifically and intentionally maps the first page of memory at address 0 to allow the compiler to speculate through NULL pointers. The compiler probably is speculating in this case and the second element is not defined.

There is some option to disable this speculation in XLC.
History
Date User Action Args
2020-07-06 16:13:30David.Edelsohnsetrecipients: + David.Edelsohn, skrah, Michael.Felt, lys.nikolaou, pablogsal
2020-07-06 16:13:30David.Edelsohnsetmessageid: <1594052010.85.0.0019685733702.issue41215@roundup.psfhosted.org>
2020-07-06 16:13:30David.Edelsohnlinkissue41215 messages
2020-07-06 16:13:30David.Edelsohncreate