Displaying 9 results from an estimated 9 matches for "beforepass".
2018 Jun 07
5
RFC: Pass Execution Instrumentation interface
...hrough LLVMContext::getPassInstrumentation()
(with context owning this object).
2. every single point of Pass execution in the (new) PassManager(s)
will query
this analysis and run instrumentation call specific to a
particular point.
Instrumentation points:
bool BeforePass (PassID, PassExecutionCounter);
void AfterPass (PassID, PassExecutionCounter);
Run before/after a particular pass execution
BeforePass instrumentation call returns true if this
execution is allowed to run.
'PassID'
certain u...
2018 Jun 08
2
RFC: Pass Execution Instrumentation interface
...through LLVMContext::getPassInstrumentation()
(with context owning this object).
2. every single point of Pass execution in the (new) PassManager(s)
will query
this analysis and run instrumentation call specific to a
particular point.
Instrumentation points:
bool BeforePass (PassID, PassExecutionCounter);
void AfterPass (PassID, PassExecutionCounter);
Run before/after a particular pass execution
BeforePass instrumentation call returns true if this
execution is allowed to run.
'PassID'
certain un...
2018 Jun 07
2
RFC: Pass Execution Instrumentation interface
...this object).
>
> 2. every single point of Pass execution in the (new)
> PassManager(s)
> will query
> this analysis and run instrumentation call specific to a
> particular point.
>
> Instrumentation points:
>
> bool BeforePass (PassID, PassExecutionCounter);
> void AfterPass (PassID, PassExecutionCounter);
>
> Run before/after a particular pass execution
> BeforePass instrumentation call returns true if this
> execution is allowed to run.
>
> ...
2018 Jun 08
2
RFC: Pass Execution Instrumentation interface
...f Pass execution in the (new) PassManager(s)
>>>> will query
>>>> this analysis and run instrumentation call specific to a
>>>> particular point.
>>>>
>>>> Instrumentation points:
>>>>
>>>> bool BeforePass (PassID, PassExecutionCounter);
>>>> void AfterPass (PassID, PassExecutionCounter);
>>>>
>>>> Run before/after a particular pass execution
>>>> BeforePass instrumentation call returns true if this
>>>> exec...
2018 Jun 11
2
RFC: Pass Execution Instrumentation interface
...will query
> this analysis and run instrumentation call
> specific to a
> particular point.
>
> Instrumentation points:
>
> bool BeforePass (PassID, PassExecutionCounter);
> void AfterPass (PassID, PassExecutionCounter);
>
> Run before/after a particular pass execution
> BeforePass instrumentation call returns true if
> t...
2008 Oct 16
0
[LLVMdev] Requiring a pass to run before/after a pass? (Adding PHIs and updating uses)
On Oct 16, 2008, at 8:29 AM, Edward Lee wrote:
> Is there a simple way to require a pass, e.g., Reg2Mem/Mem2Reg, to
> run before/after my transformation pass? Or do I do something like:
One simplest way is to handle this is to add these passes around your
pass in the pass manager.
pm.add(Reg2Mem)
pm.add(MyPass)
pm.add(Mem2Reg)
>
>
> struct myOpt {
> myOpt() {
>
2008 Oct 16
2
[LLVMdev] Requiring a pass to run before/after a pass? (Adding PHIs and updating uses)
Is there a simple way to require a pass, e.g., Reg2Mem/Mem2Reg, to run
before/after my transformation pass? Or do I do something like:
struct myOpt {
myOpt() {
mBefore = createDemoteRegisterToMemoryPass();
mAfter = createPromoteMemoryToRegisterPass();
}
getAnalysisUsage(AU) {
AU.addRequired(my stuff);
mBefore.getAnalysisUsage(AU);
mAfter.getAnalysisUsage(AU);
}
2018 Sep 28
3
OptBisect implementation for new pass manager
...s does, so it can’t decide whether or not it
> can be skipped. The pass itself should have no idea that the OptBisect
> process even exists. So the pass manager needs some way of discovering
> whether or not a pass can be skipped.
Pass Manager's way of discovering that is to ask the BeforePass
instrumentation.
We definitely do not want to add more decision-making points into pass
manager.
The question is how OptBisect object gets the information for its decision.
> I don’t have strong feelings about how this happens. Off the cuff, it
> could be added to the pass registration in...
2018 Sep 27
4
OptBisect implementation for new pass manager
Hi Andrew,
We absolutely need to be able to generate executable programs using
> opt-bisect, so some mechanism for not skipping required passes is needed.
> It might be nice to have a mode where no passes are skipped and the IR/MIR
> is dumped when the bisect limit is reached, but I don't see that as a
> requirement.
>
At this point it makes no sense to worry about the code