Message93929
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. |
|
Date |
User |
Action |
Args |
2009-10-13 16:41:25 | mark.dickinson | set | recipients:
+ mark.dickinson, loewis, pitrou, wiget |
2009-10-13 16:41:25 | mark.dickinson | set | messageid: <1255452085.35.0.444331579389.issue6603@psf.upfronthosting.co.za> |
2009-10-13 16:41:23 | mark.dickinson | link | issue6603 messages |
2009-10-13 16:41:23 | mark.dickinson | create | |
|