search for: assume_fn

...look something like this: `__builtin_assume(foo(i) == bar(j));` will cause us to generate ``` /// Must return true! static bool llvm.assume.expression_#27(int i, int j) { return foo(i) == bar(j); } ``` and a `llvm.assume` call like this: `llvm.assume() ["assume_fn"(@llvm.assume.expression_#27, %i, %j))] So we generate the expression in a new function which we (only) tie to the `llvm.assume()` through the "assume_fn" operand bundle. This will make sure we do not accidentally evaluate the code, or assume it is evaluated and produced side...

...se us to generate > > ``` > > /// Must return true! > > static bool llvm.assume.expression_#27(int i, int j) { > > return foo(i) == bar(j); > > } > > ``` > > and a `llvm.assume` call like this: > > `llvm.assume() ["assume_fn"(@llvm.assume.expression_#27, %i, %j))] > > So we generate the expression in a new function which we (only) tie to > > the `llvm.assume()` through the "assume_fn" operand bundle. This will > > make sure we do not accidentally evaluate the code, or assume it is...

.../// Must return true! > >>> static bool llvm.assume.expression_#27(int i, int j) { > >>> return foo(i) == bar(j); > >>> } > >>> ``` > >>> and a `llvm.assume` call like this: > >>> `llvm.assume() ["assume_fn"(@llvm.assume.expression_#27, %i, %j))] > >>> So we generate the expression in a new function which we (only) tie to > >>> the `llvm.assume()` through the "assume_fn" operand bundle. This will > >>> make sure we do not accidentally evaluate t...