[Bug 42437] Wine Wiki: Building Wine - Compiler Optimizations & Call-Stacks
wine-bugs at winehq.org
wine-bugs at winehq.org
Fri Apr 20 19:06:00 CDT 2018
https://bugs.winehq.org/show_bug.cgi?id=42437
Kyle Auble <kyle.auble at zoho.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kyle.auble at zoho.com
--- Comment #4 from Kyle Auble <kyle.auble at zoho.com> ---
(In reply to Wylda from comment #0)
> Wiki link:
> https://wiki.winehq.org/Building_Wine#Compiler_Optimizations_.26_Call-Stacks
>
> Says:
> ../wine-source/configure CFLAGS="-g -O1 -fno-optimize-sibling-calls
> -fno-omit-frame-pointer -fno-inline"
>
>
> IMHO these two are superfluous as:
> * "optimize-sibling-calls" is disabled in -O1 and enabled since -O2
> * "omit-frame-pointer" is disabled in -O0, -O1 and -O2
Hi Wylda,
This section of the page came from splicing what was already on the wiki with
info from GCC & Clang docs. I never really bothered to see if they were
redundant because that shouldn't cause any problems, plus I think which
features each -O level enables can vary based on your GCC version and config.
(In reply to Austin English from comment #2)
> Actually, you may want -Og for that:
> -Og Optimize for debugging experience rather than
> speed or size.
Now, this -Og option definitely simplifies things so I've rewritten the
wiki-page to emphasize it. I think it's a relatively new feature (the GCC
release notes mention adding it in v4.8), but I imagine most distros have moved
to that version or newer by now. I've left the table of individual flags as a
note though, mainly to give the reader some context about the debug process.
If that sounds good to everybody, I think we can close the bug.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
More information about the wine-bugs
mailing list