-O2 or -O3? this brings excitement to computing!

[PedroLarroy]

BPO	12651
Nosy	@pitrou, @benjaminp

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2011-07-28.22:22:06.363>
created_at = <Date 2011-07-28.22:09:12.320>
labels = ['build']
title = '-O2 or -O3? this brings excitement to computing!'
updated_at = <Date 2011-07-28.22:22:06.361>
user = 'https://bugs.python.org/PedroLarroy'

bugs.python.org fields:

activity = <Date 2011-07-28.22:22:06.361>
actor = 'benjamin.peterson'
assignee = 'none'
closed = True
closed_date = <Date 2011-07-28.22:22:06.363>
closer = 'benjamin.peterson'
components = ['Build']
creation = <Date 2011-07-28.22:09:12.320>
creator = 'Pedro.Larroy'
dependencies = []
files = []
hgrepos = []
issue_num = 12651
keywords = []
message_count = 3.0
messages = ['141318', '141319', '141321']
nosy_count = 3.0
nosy_names = ['pitrou', 'benjamin.peterson', 'Pedro.Larroy']
pr_nums = []
priority = 'normal'
resolution = 'wont fix'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue12651'
versions = ['Python 2.7']

[PedroLarroy]

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

[pitrou]

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).

[benjaminp]

Fixed in default. It's harmless in other versions.