Displaying 2 results from an estimated 2 matches for "oaggress".
2013 Jan 14
0
[LLVMdev] [cfe-dev] RFC: Codifying (but not formalizing) the optimization levels in LLVM and Clang
...ould be against making it a reuiqrement as it will
severely limit what we do at O3 over O2.
FWIW, the Cray compiler considers O3 to be "try to make it as fast as
possible without unreasonably increasing compile time" but does not
guarantee it absolutely will be faster than -O2. We have -Oaggress for
"pull out all the stops, take days to compile the code and you get what
you get." :)
> A final note: I would like to remove all other variations on the '-O'
> flag. That includes the really strange '-O4' behavior. Whether the
> compilation is LTO should be a...
2013 Jan 14
17
[LLVMdev] RFC: Codifying (but not formalizing) the optimization levels in LLVM and Clang
This has been an idea floating around in my head for a while and after
several discussions with others it continues to hold up so I thought I
would mail it out. Sorry for cross posting to both lists, but this is an
issue that would significantly impact both LLVM and Clang.
Essentially, LLVM provides canned optimization "levels" for frontends to
re-use. This is nothing new. However, we