[issue16615] gcc 4.7 unused-but-set warnings

STINNER Victor added the comment: We are now dealing with GCC 11 warnings, I close this issue. Moreover, the GCC warnings are not mentioned. -- nosy: +vstinner resolution: -> out of date stage: -> resolved status: pending -> closed ___ Python

[issue16615] gcc 4.7 unused-but-set warnings

Irit Katriel added the comment: Is this about the pre-version 3.3 warnings? If so it can be closed. -- nosy: +iritkatriel status: open -> pending ___ Python tracker ___

[issue16615] gcc 4.7 unused-but-set warnings

Jesús Cea Avión added the comment: Spin-off of Issue #16588. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16615 ___ ___ Python-bugs-list

[issue16615] gcc 4.7 unused-but-set warnings

New submission from Jesús Cea Avión: GCC 4.7 is showing some compilation warning about setting variables never read. -- assignee: jcea messages: 176984 nosy: jcea priority: normal severity: normal status: open title: gcc 4.7 unused-but-set warnings type: compile error versions: Python

[issue16615] gcc 4.7 unused-but-set warnings

Changes by Jesús Cea Avión j...@jcea.es: -- assignee: jcea - nosy: +christian.heimes ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16615 ___ ___