search for: winehfuncinfo

...ndexes.h: keep the SlotIndexes pass and move the rest to SlotIndex.h. Introduce a new container class in SlotIndex.h that will extract the map between machine instructions and slot indexes from the SlotIndexes pass and remove the dependency on the pass from MachineBasicBlock's print method. - WinEHFuncInfo - Either move parseEHInfo from WinEHPrepare.cpp to new file WinEHFuncInfo.cpp or move the declaration of parseEHInfo from WinEHFuncInfo.h to a new header WinEHPrepare.h - Get rid of several unused #includes in MachineIR cpp files that include passes. After that it should be possible to move the...

...keep the SlotIndexes pass and move the rest to SlotIndex.h. Introduce a new container class in SlotIndex.h that will extract the map > between machine instructions and slot indexes from the SlotIndexes pass and remove the dependency on the pass from MachineBasicBlock's print method. > - WinEHFuncInfo - Either move parseEHInfo from WinEHPrepare.cpp to new file WinEHFuncInfo.cpp or move the declaration of parseEHInfo from WinEHFuncInfo.h > to a new header WinEHPrepare.h > - Get rid of several unused #includes in MachineIR cpp files that include passes. > > After that it should be p...

...e SlotIndexes pass and move the rest to SlotIndex.h. Introduce a new container class in SlotIndex.h that will extract the map >> between machine instructions and slot indexes from the SlotIndexes pass and remove the dependency on the pass from MachineBasicBlock's print method. >> - WinEHFuncInfo - Either move parseEHInfo from WinEHPrepare.cpp to new file WinEHFuncInfo.cpp or move the declaration of parseEHInfo from WinEHFuncInfo.h >> to a new header WinEHPrepare.h >> - Get rid of several unused #includes in MachineIR cpp files that include passes. >> >> After that...

...Code seems to verify just fine. ; #0 0x00e1afe8 llvm::X86FrameLowering::getFrameIndexReference(class llvm::MachineFunction const &,int,unsigned int &)const c:\p\llvm\llvm\lib\target\x86\x86framelowering.cpp:1672:0 ; #1 0x00f99010 llvm::WinException::getFrameIndexOffset(int,struct llvm::WinEHFuncInfo const &) c:\p\llvm\llvm\lib\codegen\asmprinter\winexception.cpp:320:0 ; #2 0x00f97f75 llvm::WinException::emitCXXFrameHandler3Table(class llvm::MachineFunction const *,bool) c:\p\llvm\llvm\lib\codegen\asmprinter\winexception.cpp:805:0 ; #3 0x00f98e77 llvm::WinException::endFunction(class ll...

...; #0 0x00e1afe8 llvm::X86FrameLowering::getFrameIndexReference(class >> llvm::MachineFunction const &,int,unsigned int &)const >> c:\p\llvm\llvm\lib\target\x86\x86framelowering.cpp:1672:0 >> ; #1 0x00f99010 llvm::WinException::getFrameIndexOffset(int,struct >> llvm::WinEHFuncInfo const &) >> c:\p\llvm\llvm\lib\codegen\asmprinter\winexception.cpp:320:0 >> ; #2 0x00f97f75 llvm::WinException::emitCXXFrameHandler3Table(class >> llvm::MachineFunction const *,bool) >> c:\p\llvm\llvm\lib\codegen\asmprinter\winexception.cpp:805:0 >> ; #3 0x00f98e77...

...he object file for this information altogether; MCJit could add a hook where a client could insert passes into the PassManager used in emitObject; LLILC could attach a pass that would consult the MachineModuleInfo, where this information could be stored (it's similar to what's stored in the WinEHFuncInfos hanging off the MMI today). But adding hooks for client passes might be opening a can of worms... My inclination would be #2 or #3, but I would love some feedback on which of the tradeoffs seem most agreeable (and/or what options I've overlooked). Thanks -Joseph -------------- next part --...

...he object file for this information altogether; MCJit could add a hook where a client could insert passes into the PassManager used in emitObject; LLILC could attach a pass that would consult the MachineModuleInfo, where this information could be stored (it's similar to what's stored in the WinEHFuncInfos hanging off the MMI today). But adding hooks for client passes might be opening a can of worms… My inclination would be #2 or #3, but I would love some feedback on which of the tradeoffs seem most agreeable (and/or what options I've overlooked). Thanks -Joseph ____________________________...

...his > information altogether; MCJit could add a hook where a client could insert > passes into the PassManager used in emitObject; LLILC could attach a pass > that would consult the MachineModuleInfo, where this information could be > stored (it's similar to what's stored in the WinEHFuncInfos hanging off the > MMI today). But adding hooks for client passes might be opening a can of > worms… > > > > My inclination would be #2 or #3, but I would love some feedback on which > of the tradeoffs seem most agreeable (and/or what options I've overlooked). > > &g...

On Wed, May 27, 2015 at 8:15 AM Chris Lattner <clattner at apple.com> wrote: > On May 26, 2015, at 11:20 PM, Quentin Colombet <qcolombet at apple.com> > wrote: > > +1. > > Could those two be subdirectories of one “Machine-Related-Stuff” directory? > E.g., > MachineStuff/IR > MachineStuff/CodeGen > > Where MachineStuff is something meaningful :). >

...he object file for this information altogether; MCJit could add a hook where a client could insert passes into the PassManager used in emitObject; LLILC could attach a pass that would consult the MachineModuleInfo, where this information could be stored (it's similar to what's stored in the WinEHFuncInfos hanging off the MMI today). But adding hooks for client passes might be opening a can of worms… My inclination would be #2 or #3, but I would love some feedback on which of the tradeoffs seem most agreeable (and/or what options I've overlooked). Thanks -Joseph ____________________________...

...he object file for this information altogether; MCJit could add a hook where a client could insert passes into the PassManager used in emitObject; LLILC could attach a pass that would consult the MachineModuleInfo, where this information could be stored (it's similar to what's stored in the WinEHFuncInfos hanging off the MMI today). But adding hooks for client passes might be opening a can of worms… My inclination would be #2 or #3, but I would love some feedback on which of the tradeoffs seem most agreeable (and/or what options I've overlooked). Thanks -Joseph ____________________________...

...he object file for this information altogether; MCJit could add a hook where a client could insert passes into the PassManager used in emitObject; LLILC could attach a pass that would consult the MachineModuleInfo, where this information could be stored (it's similar to what's stored in the WinEHFuncInfos hanging off the MMI today). But adding hooks for client passes might be opening a can of worms… My inclination would be #2 or #3, but I would love some feedback on which of the tradeoffs seem most agreeable (and/or what options I've overlooked). Thanks -Joseph ____________________________...