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 | gvanrossum |
|---|---|
| Recipients | donmez, gregory.p.smith, gvanrossum, loewis, theller |
| Date | 2008年01月09日.17:46:04 |
| SpamBayes Score | 0.07624191 |
| Marked as misclassified | No |
| Message-id | <1199900767.94.0.485912848668.issue1608@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
It would actually be better to use -fno-strict-overflow instead of -fwrapv, if it exists (GCC 4.2 and later). See also http://bugs.python.org/issue1621 which suggests there aren't actually many places that need this; gcc -Wstrict-overflow should help auditing the code. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年01月09日 17:46:08 | gvanrossum | set | spambayes_score: 0.0762419 -> 0.07624191 recipients: + gvanrossum, loewis, theller, gregory.p.smith, donmez |
| 2008年01月09日 17:46:07 | gvanrossum | set | spambayes_score: 0.0762419 -> 0.0762419 messageid: <1199900767.94.0.485912848668.issue1608@psf.upfronthosting.co.za> |
| 2008年01月09日 17:46:04 | gvanrossum | link | issue1608 messages |
| 2008年01月09日 17:46:04 | gvanrossum | create | |