search for: stdopt

Displaying 4 results from an estimated 4 matches for "stdopt".

Did you mean: stdint
2013 Jan 14
1
[LLVMdev] [cfe-dev] RFC: Codifying (but not formalizing) the optimization levels in LLVM and Clang
...nt and putting "opt" at the end. > > I would still like something other than "opt" for the fourth one. "opt" > seems too generic given the other levels. > I agree that having just "opt" seems too generic in comparison. Maybe something like "stdopt" (or even the longer "balancedopt") since it corresponds to -O2 and is intended to represent a good optimization level for most cases with a balance of compile time, space, and runtime efficiency. - Kaelyn -------------- next part -------------- An HTML attachment was scrubbed... UR...
2013 Jan 14
0
[LLVMdev] [cfe-dev] RFC: Codifying (but not formalizing) the optimization levels in LLVM and Clang
Chandler Carruth <chandlerc at gmail.com> writes: > minsizeopt > sizeopt > quickopt > opt > maxopt I prefer being consistent and putting "opt" at the end. I would still like something other than "opt" for the fourth one. "opt" seems too generic given the other levels. -David
2013 Jan 14
0
[LLVMdev] [cfe-dev] RFC: Codifying (but not formalizing) the optimization levels in LLVM and Clang
...at the end. >> >> I would still like something other than "opt" for the fourth one. "opt" >> seems too generic given the other levels. >> > > I agree that having just "opt" seems too generic in comparison. Maybe > something like "stdopt" (or even the longer "balancedopt") since it > corresponds to -O2 and is intended to represent a good optimization level > for most cases with a balance of compile time, space, and runtime > efficiency. > I don't like a qualifier because all the qualifiers I tried do...
2013 Jan 14
4
[LLVMdev] [cfe-dev] RFC: Codifying (but not formalizing) the optimization levels in LLVM and Clang
On Mon, Jan 14, 2013 at 4:46 AM, Justin Holewinski < justin.holewinski at gmail.com> wrote: > If I understand the attributes correctly, they would be function-level > attributes applied to IR functions, correct? I'm curious what the > semantics would be for cross-function optimization. For example, consider > a function "foo" defined with maxopt and a function