Author tim.peters
Recipients paul.moore, r.david.murray, serhiy.storchaka, steve.dower, tim.golden, tim.peters, vstinner, zach.ware
Date 2015-09-05.22:11:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441491094.55.0.189513682269.issue24999@psf.upfronthosting.co.za>
In-reply-to
Content
The longobject.c warnings are almost certainly unrelated to the test_re crash.

If shifting right twice (adding parens for clarity):

    (LONG_MAX >> PyLong_SHIFT) >> PyLong_SHIFT.

squashes the warnings, that would be a substantially clearer way to express the intent than the

    SIZEOF_LONG*CHAR_BIT-1 >= 2*PyLong_SHIFT

spelling.  Adding a comment *explaining* the intent would be even better.

For the segfault issue, best guess is that it's a compiler optimization bug.  Not common as mud, or even as common as nuisance warnings, but not all that rare either ;-)
History
Date User Action Args
2015-09-05 22:11:34tim.peterssetrecipients: + tim.peters, paul.moore, vstinner, tim.golden, r.david.murray, zach.ware, serhiy.storchaka, steve.dower
2015-09-05 22:11:34tim.peterssetmessageid: <1441491094.55.0.189513682269.issue24999@psf.upfronthosting.co.za>
2015-09-05 22:11:34tim.peterslinkissue24999 messages
2015-09-05 22:11:34tim.peterscreate