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: -O2 or -O3? this brings excitement to computing!
Type: Stage:
Components: Build Versions: Python 2.7
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: Nosy List: Pedro.Larroy, benjamin.peterson, pitrou
Priority: normal Keywords:

Created on 2011-07-28 22:09 by Pedro.Larroy, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (3)
msg141318 - (view) Author: Pedro Larroy (Pedro.Larroy) Date: 2011-07-28 22:09
When I build it compiles with both -O2 and -O3...

this is debian testing on amd64.

gcc -pthread -c -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes  -I. -IInclude -I./Include   -DPy_BUILD_CORE -o Python/getcompiler.o Python/getcompiler.c
msg141319 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2011-07-28 22:14
AFAICT the last one (-O3) is used by the compiler and that's the desired effect (we want to compile with the highest optimization level).
msg141321 - (view) Author: Benjamin Peterson (benjamin.peterson) * (Python committer) Date: 2011-07-28 22:22
Fixed in default. It's harmless in other versions.
History
Date User Action Args
2022-04-11 14:57:20adminsetgithub: 56860
2011-07-28 22:22:06benjamin.petersonsetstatus: open -> closed

nosy: + benjamin.peterson
messages: + msg141321

resolution: wont fix
2011-07-28 22:14:02pitrousetnosy: + pitrou
messages: + msg141319
2011-07-28 22:09:12Pedro.Larroycreate