Displaying 3 results from an estimated 3 matches for "83d4e48f".
2013 Jan 14
0
[LLVMdev] [cfe-dev] RFC: Codifying (but not formalizing) the optimization levels in LLVM and Clang
...__________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130114/83d4e48f/attachment.html>
2013 Jan 14
1
[LLVMdev] [cfe-dev] RFC: Codifying (but not formalizing) the optimization levels in LLVM and Clang
On Mon, Jan 14, 2013 at 1:30 PM, <dag at cray.com> wrote:
> 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"
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