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 mark.dickinson
Recipients mark.dickinson, pitrou, serhiy.storchaka
Date 2012-07-07.11:09:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I don't see what the undefined behavior. Can you specify exactly the
> item of the Standard, in which it is mentioned?

It's C99 section 6.5, paragraph 7:  "An object shall have its stored value accessed only by an lvalue expression that has one of the following types ...".  It's the dereferencing of the pointer that's the problem: that's accessing a stored value of type 'char' by an lvalue expression that has type 'unsigned long'.

> In any case, I don't think that the original patch introduces some new
> undefined behavior.

Ah;  were the strict aliasing problems already there before the patch?  I didn't check.
Date User Action Args
2012-07-07 11:09:28mark.dickinsonsetrecipients: + mark.dickinson, pitrou, serhiy.storchaka
2012-07-07 11:09:28mark.dickinsonsetmessageid: <>
2012-07-07 11:09:28mark.dickinsonlinkissue15144 messages
2012-07-07 11:09:27mark.dickinsoncreate