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.

Title: If compile with gcc 4.3.0 python interpreter itself eats all memory
Type: Stage:
Components: Interpreter Core Versions: 3rd party
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: loewis, orivej
Priority: normal Keywords:

Created on 2008-04-12 23:30 by orivej, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (3)
msg65426 - (view) Author: Orivej Desh (orivej) * Date: 2008-04-12 23:30
First time I noticed it during compilation of python3 r62301, then 
3.0a4, then 3.0a3, with and without CFLAGS set. 
Step "./python -E ./ -q build" called by make never ends (and 
there is no output). Just "/python" behaves the same: it eats memory 
and prints nothing. Gcc 3.4.6 works fine. Previous versions of gcc 4 
were working too, but I didn`t tested them now.
My system: gcc 4.3.0, kernel 2.6.24.zen5.20080410 (with zen patchset, 
can test again with vanilla 2.6.24, or if you say it is too old I will 
compile, glibc 2.7, Arch GNU/Linux.
msg65428 - (view) Author: Orivej Desh (orivej) * Date: 2008-04-12 23:59
This doesn't affect python 2.5.2
msg65435 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2008-04-13 04:32
That's a bug in gcc 4.3, see
Date User Action Args
2022-04-11 14:56:33adminsetgithub: 46878
2008-04-13 04:32:47loewissetstatus: open -> closed
resolution: not a bug
messages: + msg65435
nosy: + loewis
versions: + 3rd party, - Python 3.0
2008-04-12 23:59:07orivejsetmessages: + msg65428
2008-04-12 23:30:01orivejcreate