Mark Dickinson <dicki...@gmail.com> added the comment: 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6603> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
