search for: getoptimizationlevel

On Fri, Nov 15, 2013 at 11:19 AM, Umesh Kalappa <umesh.kalappa0 at gmail.com> wrote: > Hi Aaron, > >>>Why is getLastArgIntValue being called twice in the first place? > > It has been called from the getOptimizationLevel() ,which in turn called by > methods like ParseCodeGenArgs() and ParseLangArgs(), > > where method getOptimizationLevel() register the "invalid integral value" > diagnostics in the diagnostics engine twice ,since it was called twice. > > So i added the flag to check if t...

Hi All, Clang pop up with the "error: invalid integral value" diagnostics twice ,when you enable the optimization through -O with a non-integer value i.e -O<non integer> as show below $ clang -Of -S test.c error: invalid integral value 'f' in '-Of' error: invalid integral value 'f' in '-Of' Attached patch fix the issue as $ clang -Of -S

...s requires a non-trivial > refactoring. I don't have particularly bright ideas on solving it, but > I'm uncomfortable adding the flag at the arg level because it kind of > encourages lazy design when handling args. Perhaps looking into ways > the code could be refactored so that getOptimizationLevel() is only > called once (and perhaps the results get cached somewhere) would be a > good approach. I completely agree with you, Aaron. Chad

...http://lists.llvm.org/pipermail/llvm-dev/2016-November/107006.html which discussed debug information for optimized code. At the end of that discussion, Adrian broached the interest in making -O1 only enable optimizations. I see in the code ( *clang/lib/Frontend/CompilerInvocation.cpp*, in function *getOptimizationLevel*) that *-Og* option is equivalent to *-O1*. Does this mean any progress on making *-O1* the GCC's *-Og*? If not, would someone kindly tell me what is holding the debuggability at *-O1* back? Which optimization passes are removing our debug info at this *-O1* level? Thank you for your help, So...

...16) http://lists.llvm.org/pipermail/llvm-dev/2016-November/107006.html which discussed debug information for optimized code. At the end of that discussion, Adrian broached the interest in making -O1 only enable optimizations. I see in the code (clang/lib/Frontend/CompilerInvocation.cpp, in function getOptimizationLevel) that -Og option is equivalent to -O1. Does this mean any progress on making -O1 the GCC's -Og? If not, would someone kindly tell me what is holding the debuggability at -O1 back? Which optimization passes are removing our debug info at this -O1 level? Thank you for your help, Son Tuan Vu ---...

...t; pipermail/llvm-dev/2016-November/107006.html which discussed debug > information for optimized code. At the end of that discussion, Adrian > broached the interest in making -O1 only enable optimizations. I see in > the code (*clang/lib/Frontend/CompilerInvocation.cpp*, in function > *getOptimizationLevel*) that *-Og* option is equivalent to *-O1*. Does > this mean any progress on making *-O1* the GCC's *-Og*? If not, would > someone kindly tell me what is holding the debuggability at *-O1* back? > Which optimization passes are removing our debug info at this * -O1* > level? > &gt...

...16) http://lists.llvm.org/pipermail/llvm-dev/2016-November/107006.html which discussed debug information for optimized code. At the end of that discussion, Adrian broached the interest in making -O1 only enable optimizations. I see in the code (clang/lib/Frontend/CompilerInvocation.cpp, in function getOptimizationLevel) that -Og option is equivalent to -O1. Does this mean any progress on making -O1 the GCC's -Og? If not, would someone kindly tell me what is holding the debuggability at -O1 back? Which optimization passes are removing our debug info at this -O1 level? > > > > Thank you for your...

Test cases? Also, this seems a bit heavy-handed for a solution. Why is getLastArgIntValue being called twice in the first place? ~Aaron On Fri, Nov 15, 2013 at 6:35 AM, Umesh Kalappa <umesh.kalappa0 at gmail.com> wrote: > Hi All, > > Clang pop up with the "error: invalid integral value" diagnostics twice > ,when you enable the optimization through -O with a

...> pipermail/llvm-dev/2016-November/107006.html which discussed debug > information for optimized code. At the end of that discussion, Adrian > broached the interest in making -O1 only enable optimizations. I see in the > code (clang/lib/Frontend/CompilerInvocation.cpp, in function > getOptimizationLevel) that -Og option is equivalent to -O1. Does this mean > any progress on making -O1 the GCC's -Og? If not, would someone kindly tell > me what is holding the debuggability at -O1 back? Which optimization passes > are removing our debug info at this -O1 level? > > > > > &g...

...sses A,C,E on it. In the case of Fun3, the PassManager will run B,C,E. 3.2 How to deal with size levels -------------------------------- By default, clang sets the optimization level to 2 when either option "-Os" or "-Oz" is specified. See for example in clang how function `getOptimizationLevel' is implemented (in File lib/Frontend/CompilerInvocation.cpp). This is also true for the 'opt' tool but not for bugpoint which only accepts options -O1, -O2, -O3 to control the optimization level. In addition to "-Os" and "-Oz" clang also accepts option "-O&quo...