Displaying 2 results from an estimated 2 matches for "doinitializaton".
Did you mean:
doinitialization
2004 Jun 24
3
[LLVMdev] Pass vs. FunctionPass
...fine, but the
latter looks like this:
bool FunctionPass::run(Function &F) {
if (F.isExternal()) return false;// Passes are not run on external
functions!
return doInitialization(*F.getParent()) | runOnFunction(F)
| doFinalization(*F.getParent());
}
So, with FunctionPassManager, doInitializaton will be called once for each
function, which is strange, given that that method takes Module&. When this
behaviour is desirable?
- Volodya
2004 Jun 24
0
[LLVMdev] Pass vs. FunctionPass
...gt; bool FunctionPass::run(Function &F) {
> if (F.isExternal()) return false;// Passes are not run on external
> functions!
>
> return doInitialization(*F.getParent()) | runOnFunction(F)
> | doFinalization(*F.getParent());
> }
>
> So, with FunctionPassManager, doInitializaton will be called once for
> each function, which is strange, given that that method takes Module&.
> When this behaviour is desirable?
That *is* odd, I've never noticed that code before. I think that the
FunctionPassManager is only used by the JIT. For normal optimization and
static...