➜

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.

classification
Title: gcc 4.7 unused-but-set warnings
Type: compile error Stage: resolved
Components: Versions: Python 3.2, Python 3.3, Python 3.4, Python 2.7
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: christian.heimes, iritkatriel, jcea, vstinner
Priority: normal Keywords:

Created on 2012-12-05 13:45 by jcea, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (4)
msg176984 - (view) Author: Jesús Cea Avión (jcea) * (Python committer) Date: 2012-12-05 13:45 
GCC 4.7 is showing some compilation warning about setting variables never read.
msg176985 - (view) Author: Jesús Cea Avión (jcea) * (Python committer) Date: 2012-12-05 13:45 
Spin-off of Issue #16588.
msg384940 - (view) Author: Irit Katriel (iritkatriel) * (Python committer) Date: 2021-01-12 14:34 
Is this about the pre-version 3.3 warnings? If so it can be closed.
msg384941 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2021-01-12 14:36 
We are now dealing with GCC 11 warnings, I close this issue. Moreover, the GCC warnings are not mentioned.
History
Date User Action Args
2022-04-11 14:57:39adminsetgithub: 60819
2021-01-12 14:36:34vstinnersetstatus: pending -> closed

nosy: + vstinner
messages: + msg384941

resolution: out of date
stage: resolved
2021-01-12 14:34:24iritkatrielsetstatus: open -> pending
nosy: + iritkatriel
messages: + msg384940

2012-12-05 14:21:02jceasetassignee: jcea ->

nosy: + christian.heimes
2012-12-05 13:45:39jceasetmessages: + msg176985
2012-12-05 13:45:09jceacreate