[issue10951] gcc 4.6 warnings

Martin v. Löwis added the comment: I don't mind them being backported, in the spirit of supporting newer tools well in 2.7. OTOH, I don't see it as necessary, either. 2.7 will eventually be phased out, and then it doesn't matter how much warnings it produces. -- __

[issue10951] gcc 4.6 warnings

Serhiy Storchaka added the comment: What about backporting this fixes to 2.7? -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Py

[issue10951] gcc 4.6 warnings

Changes by STINNER Victor : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue10951] gcc 4.6 warnings

STINNER Victor added the comment: fix_2warnings.diff: I don't like statement like (void)err; to kill a compiler warning. I prefer GCC __attribute__((unused)) using a macro instead. About the change on unicode_fromascii, the code changed a lot since the patch was written. The patch is outdated

[issue10951] gcc 4.6 warnings

Martin Pool added the comment: Hi, Martin, On 20 August 2012 05:25, Martin v. Löwis wrote: > Martin v. Löwis added the comment: > > (As usual), I'm quite skeptical about this "bulk bug report"; it violates the > "one bug at a time" principle, where "one bug" can roughly be defined as > "canno

[issue10951] gcc 4.6 warnings

Martin v. Löwis added the comment: (As usual), I'm quite skeptical about this "bulk bug report"; it violates the "one bug at a time" principle, where "one bug" can roughly be defined as "cannot be split into smaller independent issues". For the cases at hand, I think it would be best if somebo

[issue10951] gcc 4.6 warnings

Roundup Robot added the comment: New changeset 2f10c1ad4b21 by Ross Lagerwall in branch 'default': Issue #10951: Fix warnings in the socket module. http://hg.python.org/cpython/rev/2f10c1ad4b21 New changeset 1dd43e939c07 by Ross Lagerwall in branch 'default': Issue #10951: Fix compiler warnings

[issue10951] gcc 4.6 warnings

Roundup Robot added the comment: New changeset d7862e855274 by Victor Stinner in branch '3.2': Issue #10951: Fix a compiler warning in timemodule.c http://hg.python.org/cpython/rev/d7862e855274 New changeset 49b85dba251d by Victor Stinner in branch 'default': Issue #10951: Fix compiler warnings

[issue10951] gcc 4.6 warnings

Jérémy Anger added the comment: I've fixed two more warnings, see my patch. (gcc 4.6.2) -- nosy: +kidanger Added file: http://bugs.python.org/file24004/fix_2warnings.diff ___ Python tracker ___

[issue10951] gcc 4.6 warnings

Martin Pool added the comment: My patch above fixes all the messages so that you get a clean build with the current makefile. -Wuninitialized and 'offset outside constant string' would be worth fixing but I can't reproduce them in Python. I'm personally not so keen on fixing all the signed/u

[issue10951] gcc 4.6 warnings

Martin Pool added the comment: This fixes every compiler warning so that Python build with -Werror on Ubuntu Oneiric alpha (gcc 4.6.1-7ubuntu1). * PyMem_Resize is a macro that mutates its first argument; the return value shouldn't be used. * Some variables in sre are (apparently harmlessl

[issue10951] gcc 4.6 warnings

Martin Pool added the comment: this fixes the pickle warnings, and cleans up some (I'm pretty sure) dead code in there. the pickle tests all pass. -- keywords: +patch nosy: +poolie Added file: http://bugs.python.org/file22980/20110822-1150-python-warnings.diff ___

[issue10951] gcc 4.6 warnings

Brett Cannon added the comment: You're right, Terry. It's a judgment call as to what should be simply deleted compared to commented out. -- ___ Python tracker ___ _

[issue10951] gcc 4.6 warnings

Terry J. Reedy added the comment: I can see how a comment like /* spam = eggs + ham */ could be useful, but and isolated /* foo = 0 */ where 'foo' appears nowhere else in the file seems more like confusing noise. -- ___ Python tracker

[issue10951] gcc 4.6 warnings

Brett Cannon added the comment: Just a comment on those warnings about unused assignments; think about commenting them out instead of flat-out deleting them. When I ran clang over Python 2.7 I got some blow-back from deleting some assignments as some found them to be like documentation. In in

[issue10951] gcc 4.6 warnings

STINNER Victor added the comment: gcc 4.6 bug has been fixed (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47271). So setup.py can compile extensions using gcc 4.6, and here are new warnings: --- building dbm using bdb /home/haypo/prog/GIT/py3k/Modules/_pickle.c: In function 'load': /home/haypo/

[issue10951] gcc 4.6 warnings

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue10951] gcc 4.6 warnings

Terry J. Reedy added the comment: I took a look at an example of each type. Sign-compare, Parser/node.c, 94 if (required_capacity > PY_SIZE_MAX / sizeof(node)) I presume PY_SIZE_MAX and sizeof(node) are both unsigned. So is, conceptually, required_capacity, but it is defined as an int

[issue10951] gcc 4.6 warnings

Changes by Brett Cannon : -- nosy: +brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue10951] gcc 4.6 warnings

Changes by STINNER Victor : -- components: +Build versions: +Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue10951] gcc 4.6 warnings

New submission from STINNER Victor : To analyze #9880, I installed gcc-4.6. It looks like this new gcc version emits new warnings. Here is a report of py3k warnings generated with "gcc-4.6 -O3 -Wall -Wextra -Wstrict-prototypes -Wno-missing-field-initializers -Wno-unused-parameter" on AMD64. I