Message 272500 - Python tracker

➜

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	martin.panter
Recipients	martin.panter, serhiy.storchaka, skrah, vstinner, ztane
Date	2016-08-12.05:54:27
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1470981268.17.0.233844073723.issue23545@psf.upfronthosting.co.za>
In-reply-to

Content
I didn’t look too closely, but I did see that _ssl_locks_count is unsigned int. I was compiling for x86-64 Linux, where int is 32 bits and size_t is 64. So maybe GCC was optimizing the (size_t) cast away, and then rightfully warning that the largest unsigned int will never exceed the largest possible array size.

I didn’t look too closely, but I did see that _ssl_locks_count is unsigned int. I was compiling for x86-64 Linux, where int is 32 bits and size_t is 64. So maybe GCC was optimizing the (size_t) cast away, and then rightfully warning that the largest unsigned int will never exceed the largest possible array size.

History
Date	User	Action	Args
2016-08-12 05:54:28	martin.panter	set	recipients: + martin.panter, vstinner, skrah, serhiy.storchaka, ztane
2016-08-12 05:54:28	martin.panter	set	messageid: <1470981268.17.0.233844073723.issue23545@psf.upfronthosting.co.za>
2016-08-12 05:54:28	martin.panter	link	issue23545 messages
2016-08-12 05:54:27	martin.panter	create