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 loewis, mark.dickinson, pitrou, wiget
Date 2009-10-13.16:41:23
SpamBayes Score 1.1719736e-06
Marked as misclassified No
Message-id <1255452085.35.0.444331579389.issue6603@psf.upfronthosting.co.za>
In-reply-to
Content
I just found a more recent one:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41133

Whether this is a gcc misfeature or not, it sounds as though it's not 
going to change.

Maybe there should be two separate READ_TIMESTAMP cases?  One for x86 (or 
x86_64 in 32-bit mode), and one for x86_64 in 64-bit mode.
History
Date User Action Args
2009-10-13 16:41:25mark.dickinsonsetrecipients: + mark.dickinson, loewis, pitrou, wiget
2009-10-13 16:41:25mark.dickinsonsetmessageid: <1255452085.35.0.444331579389.issue6603@psf.upfronthosting.co.za>
2009-10-13 16:41:23mark.dickinsonlinkissue6603 messages
2009-10-13 16:41:23mark.dickinsoncreate