search for: phielemin

Displaying 20 results from an estimated 21 matches for "phielemin".

[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Oct 31
0
[LLVMdev] problem trying to write an LLVM register-allocation pass
Hi Susan, The meaning of "addRequired(X)" is that your pass needs X to be run, and for X to be preserved by all passes that run after X and before your pass. The PHIElemination and TwoAddressInstruction passes do not preserve each other, hence there's no way for the pass manager to schedule them for you if you addRequire(...) them. The trick is that CodeGen will schedule both of these passes to be run before _any_ register allocation pass (see Passes.cpp), so yo...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Oct 31
3
[LLVMdev] problem trying to write an LLVM register-allocation pass
...is still 1. Can you help with this? Thanks again! Susan On 10/31/2012 04:55 PM, Lang Hames wrote: > Hi Susan, > > The meaning of "addRequired(X)" is that your pass needs X to be run, and > for X to be preserved by all passes that run after X and before your > pass. The PHIElemination and TwoAddressInstruction passes do not > preserve each other, hence there's no way for the pass manager to > schedule them for you if you addRequire(...) them. > > The trick is that CodeGen will schedule both of these passes to be run > before _any_ register allocation pass...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Oct 31
2
[LLVMdev] problem trying to write an LLVM register-allocation pass
I'm trying to write a MachineFunctionPass to do register allocation. I have code that worked with an old version of LLVM. It does not work with llvm-3.1. (or various other versions that I've tried). The first problem is that including this line: AU.addRequiredID(TwoAddressInstructionPassID); in method getAnalysisUsage causes a runtime error: Unable to schedule 'Eliminate PHI
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 01
0
[LLVMdev] problem trying to write an LLVM register-allocation pass
...ain! > > Susan > > > On 10/31/2012 04:55 PM, Lang Hames wrote: > >> Hi Susan, >> >> The meaning of "addRequired(X)" is that your pass needs X to be run, and >> for X to be preserved by all passes that run after X and before your >> pass. The PHIElemination and TwoAddressInstruction passes do not >> preserve each other, hence there's no way for the pass manager to >> schedule them for you if you addRequire(...) them. >> >> The trick is that CodeGen will schedule both of these passes to be run >> before _any_ regi...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 01
2
[LLVMdev] problem trying to write an LLVM register-allocation pass
...; > On 10/31/2012 04:55 PM, Lang Hames wrote: > > Hi Susan, > > The meaning of "addRequired(X)" is that your pass needs X to be > run, and > for X to be preserved by all passes that run after X and before your > pass. The PHIElemination and TwoAddressInstruction passes do not > preserve each other, hence there's no way for the pass manager to > schedule them for you if you addRequire(...) them. > > The trick is that CodeGen will schedule both of these passes to > be run >...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 01
0
[LLVMdev] problem trying to write an LLVM register-allocation pass
...ng Hames wrote: >> >> Hi Susan, >> >> The meaning of "addRequired(X)" is that your pass needs X to be >> run, and >> for X to be preserved by all passes that run after X and before >> your >> pass. The PHIElemination and TwoAddressInstruction passes do not >> preserve each other, hence there's no way for the pass manager to >> schedule them for you if you addRequire(...) them. >> >> The trick is that CodeGen will schedule both of these passes to >>...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 01
2
[LLVMdev] problem trying to write an LLVM register-allocation pass
...Hi Susan, > > The meaning of "addRequired(X)" is that your pass needs > X to be > run, and > for X to be preserved by all passes that run after X > and before your > pass. The PHIElemination and TwoAddressInstruction > passes do not > preserve each other, hence there's no way for the pass > manager to > schedule them for you if you addRequire(...) them. > > The trick is that CodeGen will sched...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 01
0
[LLVMdev] problem trying to write an LLVM register-allocation pass
...>> The meaning of "addRequired(X)" is that your pass needs >> X to be >> run, and >> for X to be preserved by all passes that run after X >> and before your >> pass. The PHIElemination and TwoAddressInstruction >> passes do not >> preserve each other, hence there's no way for the pass >> manager to >> schedule them for you if you addRequire(...) them. >> >> The trick is...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 03
2
[LLVMdev] problem trying to write an LLVM register-allocation pass
...;addRequired(X)" is that your > pass needs > X to be > run, and > for X to be preserved by all passes that run > after X > and before your > pass. The PHIElemination and > TwoAddressInstruction > passes do not > preserve each other, hence there's no way for > the pass > manager to > schedule them for you if you addRequire(...) >...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 04
0
[LLVMdev] problem trying to write an LLVM register-allocation pass
...The meaning of "addRequired(X)" is that your pass needs >>> X to be >>> run, and >>> for X to be preserved by all passes that run after X >>> and before your >>> pass. The PHIElemination and TwoAddressInstruction >>> passes do not >>> preserve each other, hence there's no way for the pass >>> manager to >>> schedule them for you if you addRequire(...) them. >>> >>>...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 04
3
[LLVMdev] problem trying to write an LLVM register-allocation pass
...pass needs >> X to be >> run, and >> for X to be preserved by all passes that >> run after X >> and before your >> pass. The PHIElemination and >> TwoAddressInstruction >> passes do not >> preserve each other, hence there's no >> way for the pass >> manager to >> schedule...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 05
0
[LLVMdev] problem trying to write an LLVM register-allocation pass
..."addRequired(X)" is that your pass needs >>>> X to be >>>> run, and >>>> for X to be preserved by all passes that run after X >>>> and before your >>>> pass. The PHIElemination and TwoAddressInstruction >>>> passes do not >>>> preserve each other, hence there's no way for the pass >>>> manager to >>>> schedule them for you if you addRequire(...) them. >>>&gt...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 05
2
[LLVMdev] problem trying to write an LLVM register-allocation pass
...X to be >>> run, and >>> for X to be preserved by all passes >>> that run after X >>> and before your >>> pass. The PHIElemination and >>> TwoAddressInstruction >>> passes do not >>> preserve each other, hence there's >>> no way for the pass >>> manager to >&g...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 07
0
[LLVMdev] problem trying to write an LLVM register-allocation pass
...> run, and >>>> for X to be preserved by all passes >>>> that run after X >>>> and before your >>>> pass. The PHIElemination and >>>> TwoAddressInstruction >>>> passes do not >>>> preserve each other, hence there's >>>> no way for the pass >>>>...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 11
2
[LLVMdev] problem trying to write an LLVM register-allocation pass
...run, and >>>>>> for X to be preserved by all passes >>>>>> that run after X >>>>>> and before your >>>>>> pass. The PHIElemination and >>>>>> TwoAddressInstruction >>>>>> passes do not >>>>>> preserve each other, hence there's >>>>>> no way for the pass >&g...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 08
2
[LLVMdev] problem trying to write an LLVM register-allocation pass
...run, and >>>>> for X to be preserved by all passes >>>>> that run after X >>>>> and before your >>>>> pass. The PHIElemination and >>>>> TwoAddressInstruction >>>>> passes do not >>>>> preserve each other, hence there's >>>>> no way for the pass >>>>>...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 11
0
[LLVMdev] problem trying to write an LLVM register-allocation pass
...X to be >> run, and >> for X to be preserved by all passes >> that run after X >> and before your >> pass. The PHIElemination and >> TwoAddressInstruction >> passes do not >> preserve each other, hence there's >> no way for the pass >> manager...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 13
5
[LLVMdev] problem trying to write an LLVM register-allocation pass
...gt;>>>>>> for X to be preserved by all passes >>>>>>> that run after X >>>>>>> and before your >>>>>>> pass. The PHIElemination and >>>>>>> TwoAddressInstruction >>>>>>> passes do not >>>>>>> preserve each other, hence there's >>>>>>> no way for...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 09
0
[LLVMdev] problem trying to write an LLVM register-allocation pass
...for X to be > preserved by all passes > that run after X > and before your > pass. The > PHIElemination and > TwoAddressInstruction > passes do not > preserve each other, hence there's > no way for the pass >...
[LLVMdev] problem trying to write an LLVM register-allocation pass
2012 Nov 13
0
[LLVMdev] problem trying to write an LLVM register-allocation pass
...erved by all passes >>> that run after X >>> and before your >>> pass. >>> The PHIElemination and >>> TwoAddressInstruction >>> passes do not >>> preserve >>> each oth...