search for: noopt

...rashes and/or assertion failures; 2) The fact that pass managers are not currently designed to support per-function optimization makes it difficult to find a reasonable way to implement this new feature. About point 2. the Idea that came in my mind consisted in making passes aware of the 'noopt' attribute. In my experiment: - I added a virtual method called 'mustAlwaysRun' in class Pass that 'returns true if it is not safe to disable this pass'. If a pass does not override the default implementation of that method, then by default it will always return true (i.e. th...

...cases. > 2) The fact that pass managers are not currently designed to support > per-function optimization makes it difficult to find a reasonable way to > implement this new feature. > > About point 2. the Idea that came in my mind consisted in making passes > aware of the 'noopt' attribute. > In my experiment: > - I added a virtual method called 'mustAlwaysRun' in class Pass that > 'returns true if it is not safe to disable this pass'. > If a pass does not override the default implementation of that method, > then by default it will alwa...

...ailures; > 2) The fact that pass managers are not currently designed to support > per-function optimization makes it difficult to find a reasonable way to > implement this new feature. > > About point 2. the Idea that came in my mind consisted in making passes > aware of the 'noopt' attribute. > In my experiment: > - I added a virtual method called 'mustAlwaysRun' in class Pass that > 'returns true if it is not safe to disable this pass'. > If a pass does not override the default implementation of that method, > then by default it will alw...

...zation level for the whole compilation unit, however we do not consider this the most important use-case. Our suggestion for the name for this attribute is "optnone" which seems to be in keeping with the existing "optsize" attribute, although it could equally be called "noopt" or something else entirely. It would be exposed to Clang users through __attribute__((optnone)) or [[optnone]]. I would like to discuss this proposal with the rest of the community to share opinions and have feedback on this. =================================================== Interactio...

Hello, I want to study the individual O3 optimizations. For this I am using following commands, but unable to replicate O3 behavior. 1. Documents/clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04/bin/clang -O1 -Xclang -disable-llvm-passes -emit-llvm -S vecsum.c -o vecsum-noopt.ll 2. Documents/clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04/bin/clang -O3 -mllvm -debug-pass=Arguments -emit-llvm -S vecsum.c 3. Documents/clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04/bin/opt <optimization sequence obtained in step 2> -S vecsum-noopt.ll -S -o o3-chk.ll Why the IR obta...

...EC/Sandbox.sh bugpoint- train Output/176.gcc.bugpoint-opt /Users/sabre/cvs/benchmarks/ speccpu2000/benchspec/CINT2000/176.gcc/data/train/input/ \ PWD=/Volumes/Data/Users/sabre/llvm/projects/llvm-test/External/ SPEC/CINT2000/176.gcc /Users/sabre/llvm/Debug/bin/bugpoint -llc- safe ../176.gcc.noopt-llvm.bc -std-compile-opts \ -append-exit-code -Xlinker=-lm -input=/dev/null -output=../ 176.gcc.out-nat -timeout=500 --tool-args -asm-verbose=false -O3 --args -- cp-decl.i -o - -quiet Running: PWD=/Volumes/Data/Users/sabre/llvm/projects/llvm-test/ External/SPEC/CINT2000/176.gcc /Users/...

...i32, i8*)*)(i32 %0, i8* %1) ret void Into something like: %8 = tail call i32 @MyMethod(i32 %0, i8* %1, %Type* null) ret void I realize I'm losing a parameter there, but this is an interface jump trick I use and relies on the end code being a 'jmp' (x86). I realize i can probably use noopt & noinline to do this trick, but I do want llvm to optimize and inline calls if it can prove it always calls a given method. Any way i can do this? -- Carlo Kok RemObjects Software

...ot;cd "; Exec += env_pwd; Perhaps I shouldn't have added it to Makefile.spec? At the least it seems like it should probably move to the beginning of the command, like this: PWD=$(CURDIR) $(SPEC_SANDBOX) bugpoint-$(RUN_TYPE) $@ $(REF_IN_DIR) \ $(LBUGPOINT) -llc-safe ../$*.noopt-llvm.bc -std-compile-opts $ (OPTPASSES) \ David On Aug 30, 2009, at 8:25 PM, Chris Lattner wrote: > Hi David, > > It looks like you added the PWD= magic to Makefile.spec. It is > preventing me from running bugpoint on the desktop, with errors like > this: > > /Users/s...

...asked how to receive unoptimized IR. This way: clang -S -emit-llvm -O3 -mllvm -disable-llvm-optzns memset.c -o memset.s I have noticed, that in any case, when I use O1, O2, O3 and disable optimizations, I still get llvm intrinsics functions inserted. when I put O0, I have no intrinsics, but have noopt attribute. Is there a way to receive purely unoptimizaed IR without any intrinsics? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170710/60f4ebbb/attachment.html>

...disable all module passes in a TU which contains a single one of these? I'll be unhappy if we need to litter checks throughout the module passes that determine whether a given instruction is inside an unoptimizable function or not. Saying that module passes are exempt from checking the 'noopt' attribute is fine to me, but then somebody needs to know how to module passes (and users may be surprised to discover that adding such an annotation to one function will cause seemingly-unrelated functions to become less optimized). Nick > The use-case is to be able to selectively disa...

...want to study the individual O3 optimizations. For this I am using > > following commands, but unable to replicate O3 behavior. > > > > 1. Documents/clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04/bin/clang -O1 > > -Xclang -disable-llvm-passes -emit-llvm -S vecsum.c -o vecsum-noopt.ll > > > > 2. Documents/clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04/bin/clang -O3 > > -mllvm -debug-pass=Arguments -emit-llvm -S vecsum.c > > > > 3. Documents/clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04/bin/opt > > <optimization sequence obtained in step...

...g like: >> %8 = tail call i32 @MyMethod(i32 %0, i8* %1, %Type* null) >> ret void >> >> I realize I'm losing a parameter there, but this is an interface jump >> trick I use and relies on the end code being a 'jmp' (x86). I realize i can >> probably use noopt & noinline to do this trick, but I do want llvm to >> optimize and inline calls if it can prove it always calls a given method. >> Any way i can do this? >> >> -- >> Carlo Kok >> RemObjects Software >> _______________________________________________ &gt...

...ual O3 optimizations. For this I am using >> > following commands, but unable to replicate O3 behavior. >> > >> > 1. Documents/clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04/bin/clang >> -O1 >> > -Xclang -disable-llvm-passes -emit-llvm -S vecsum.c -o vecsum-noopt.ll >> > >> > 2. Documents/clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04/bin/clang >> -O3 >> > -mllvm -debug-pass=Arguments -emit-llvm -S vecsum.c >> > >> > 3. Documents/clang+llvm-9.0.0-x86_64-linux-gnu-ubuntu-18.04/bin/opt >> > <optim...

...PointerCompress::getAnalysisUsage tries to register the the BU pass as required. I.e. when AU.addRequired<CompleteBUDataStructures>(); is called. $ opt -f -load ~/Projects/llvmstuff/opt/poolalloc/lib/ libpoolalloc.dylib -raiseallocs -poolalloc-passing-all-pools - pointercompress llist-noopt.bc -o llist-dp.bc Assertion failed: ((P->getPotentialPassManagerType() < RequiredPass- >getPotentialPassManagerType()) && "Unable to handle Pass that requires lower level Analysis pass"), function addLowerLevelRequiredPass, file ~/Projects/llvmstuff/llvm/lib/VMCore...

...sUsage tries to register > the the BU pass as required. I.e. when > AU.addRequired<CompleteBUDataStructures>(); is called. > > > $ opt -f -load ~/Projects/llvmstuff/opt/poolalloc/lib/ > libpoolalloc.dylib -raiseallocs -poolalloc-passing-all-pools - > pointercompress llist-noopt.bc -o llist-dp.bc > > Assertion failed: ((P->getPotentialPassManagerType() < RequiredPass- > >getPotentialPassManagerType()) && "Unable to handle Pass that > requires lower level Analysis pass"), function > addLowerLevelRequiredPass, file ~/Projects/llvmst...

I have worked quite a bit with CentOS 4.x with SAN, multipathing, LVM etc. The way I mount my file systems is using a script that is called during startup that runs fsck, imports the physical volumes, and volume groups, activates the logical volumes, creates the mount point if needed then mounts the volume, I mainly made it for software iSCSI due to the iscsi stack loading after the system mount

...sUsage tries to register > the the BU pass as required. I.e. when > AU.addRequired<CompleteBUDataStructures>(); is called. > > > $ opt -f -load ~/Projects/llvmstuff/opt/poolalloc/lib/ > libpoolalloc.dylib -raiseallocs -poolalloc-passing-all-pools - > pointercompress llist-noopt.bc -o llist-dp.bc > > Assertion failed: ((P->getPotentialPassManagerType() < RequiredPass- > >getPotentialPassManagerType()) && "Unable to handle Pass that > requires lower level Analysis pass"), function > addLowerLevelRequiredPass, file ~/Projects/llvmst...

...;> the the BU pass as required. I.e. when >> AU.addRequired<CompleteBUDataStructures>(); is called. >> >> >> $ opt -f -load ~/Projects/llvmstuff/opt/poolalloc/lib/ >> libpoolalloc.dylib -raiseallocs -poolalloc-passing-all-pools - >> pointercompress llist-noopt.bc -o llist-dp.bc >> >> Assertion failed: ((P->getPotentialPassManagerType() < RequiredPass- >> >getPotentialPassManagerType()) && "Unable to handle Pass that >> requires lower level Analysis pass"), function >> addLowerLevelRequiredPass, fi...

...whole compilation unit, however we > do not consider this the most important use-case. > > Our suggestion for the name for this attribute is "optnone" which seems to > be in keeping with the existing "optsize" attribute, although it could > equally be called "noopt" or something else entirely. It would be exposed > to Clang users through __attribute__((optnone)) or [[optnone]]. > > I would like to discuss this proposal with the rest of the community to > share opinions and have feedback on this. > > ====================================...

...t, however we >> do not consider this the most important use-case. >> >> Our suggestion for the name for this attribute is "optnone" which seems to >> be in keeping with the existing "optsize" attribute, although it could >> equally be called "noopt" or something else entirely. It would be exposed >> to Clang users through __attribute__((optnone)) or [[optnone]]. >> >> I would like to discuss this proposal with the rest of the community to >> share opinions and have feedback on this. >> >> ==========...