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 bkabrda
Recipients Arfrever, bkabrda
Date 2013-05-21.09:59:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1369130376.03.0.256804549216.issue18028@psf.upfronthosting.co.za>
In-reply-to
Content
Actually, this appears on vanilla Python 3.3 with -DWITH_TSC:

Python/ceval.c: In function ‘PyEval_EvalFrameEx’:
Python/ceval.c:986:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
     READ_TIMESTAMP(inst0);
     ^
Python/ceval.c:987:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
     READ_TIMESTAMP(inst1);
     ^
Python/ceval.c:988:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
     READ_TIMESTAMP(loop0);
     ^
Python/ceval.c:989:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
     READ_TIMESTAMP(loop1);
     ^
Python/ceval.c:1225:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
             READ_TIMESTAMP(inst1);
             ^
Python/ceval.c:1234:9: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
         READ_TIMESTAMP(loop0);
         ^
Python/ceval.c:1348:9: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
         READ_TIMESTAMP(inst0);
         ^
Python/ceval.c:2334:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
             READ_TIMESTAMP(intr0);
             ^
Python/ceval.c:2338:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
             READ_TIMESTAMP(intr1);
             ^
Python/ceval.c:2353:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
             READ_TIMESTAMP(intr0);
             ^
Python/ceval.c:2355:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
             READ_TIMESTAMP(intr1);
             ^
Python/ceval.c:2364:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
             READ_TIMESTAMP(intr0);
             ^
Python/ceval.c:2366:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
             READ_TIMESTAMP(intr1);
             ^
Python/ceval.c:2719:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
             READ_TIMESTAMP(intr0);
             ^
Python/ceval.c:2721:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
             READ_TIMESTAMP(intr1);
             ^
Python/ceval.c:2872:9: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
         READ_TIMESTAMP(inst1);
         ^
Python/ceval.c:2885:21: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
                     READ_TIMESTAMP(loop1);
                     ^
Python/ceval.c:3011:9: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
         READ_TIMESTAMP(loop1);
         ^
History
Date User Action Args
2013-05-21 09:59:36bkabrdasetrecipients: + bkabrda, Arfrever
2013-05-21 09:59:36bkabrdasetmessageid: <1369130376.03.0.256804549216.issue18028@psf.upfronthosting.co.za>
2013-05-21 09:59:36bkabrdalinkissue18028 messages
2013-05-21 09:59:35bkabrdacreate