search for: greaterthan

...nch and replace them with 0 on the spot). After walking up, you would walk down again with what you learned; for example you may have done %A = add %X, %Y way early on and know in this lower branch that %Y is 0, now %A = %X. PS had a full comparison lattice (not-equals, signed-lessthan-unsigned-greaterthan) and also grew constant range analysis (x < y implies x != -1 and y != 0). While I know PS removed tons of code from the .ll I was never really able to detect a runtime performance improvement; my guess is that while I was killing off lots of dead code it didn't impact the performance of...

...with 0 on the spot). After walking up, > you would walk down again with what you learned; for example you may > have done %A = add %X, %Y way early on and know in this lower branch > that %Y is 0, now %A = %X. PS had a full comparison lattice (not-equals, > signed-lessthan-unsigned-greaterthan) and also grew constant range > analysis (x < y implies x != -1 and y != 0). > > While I know PS removed tons of code from the .ll I was never really > able to detect a runtime performance improvement; my guess is that while > I was killing off lots of dead code it didn't...

...pot). After walking up, >> you would walk down again with what you learned; for example you may >> have done %A = add %X, %Y way early on and know in this lower branch >> that %Y is 0, now %A = %X. PS had a full comparison lattice (not-equals, >> signed-lessthan-unsigned-greaterthan) and also grew constant range >> analysis (x < y implies x != -1 and y != 0). >> >> While I know PS removed tons of code from the .ll I was never really >> able to detect a runtime performance improvement; my guess is that while >> I was killing off lots of dead...

Here is a new and improved version that also does the following: if the condition for a conditional branch has the form "A && B" then A, B and the condition are all replaced with "true" in the true destination (similarly for || conditions in the false destination). Also, if the condition has the form "X == Y" then X is replaced by Y everywhere in the true

...pp:115: `EqualTo' undeclared (first use this function) ast_h323.cpp:118: invalid use of undefined type `class H323_G7231Capability' ast_h323.h:70: forward declaration of `class H323_G7231Capability' ast_h323.cpp:120: `LessThan' undeclared (first use this function) ast_h323.cpp:122: `GreaterThan' undeclared (first use this function) ast_h323.cpp:124: warning: control reaches end of non-void function `H323_G7231Capability::Compare(const PObject &) const' ast_h323.cpp: At top level: ast_h323.cpp:127: invalid use of undefined type `class H323_G7231Capability' ast_h323.h:70: fo...

...p:109: `EqualTo' undeclared (first use this function) ast_h323.cpp:112: invalid use of undefined type `class H323_G7231Capability' ast_h323.h:60: forward declaration of `class H323_G7231Capability' ast_h323.cpp:114: `LessThan' undeclared (first use this function) ast_h323.cpp:116: `GreaterThan' undeclared (first use this function) ast_h323.cpp: At top level: ast_h323.cpp:121: invalid use of undefined type `class H323_G7231Capability' ast_h323.h:60: forward declaration of `class H323_G7231Capability' ast_h323.cpp: In method `PObject *H323_G7231Capability::Clone () const'...

Hi all, I wrote a little pass (attached) which does the following: if it sees a conditional branch instruction then it replaces all occurrences of the condition in the true block with "true" and in the false block with "false". Well, OK, it is a bit more sophisticated (and a bit more careful!) than that but you get the idea. It will turn this define i1 @t1(i1 %c) { br