[llvm-commits] [llvm] r49064 - in /llvm/trunk: include/llvm/CodeGen/MachineModuleInfo.h lib/CodeGen/DwarfWriter.cpp lib/CodeGen/LLVMTargetMachine.cpp lib/CodeGen/MachineModuleInfo.cpp lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp lib/Target/PowerPC/PPCAsmPrinter.cpp lib/Target/PowerPC/PPCRegisterInfo.cpp lib/Target/X86/X86ATTAsmPrinter.cpp lib/Target/X86/X86AsmPrinter.cpp lib/Target/X86/X86RegisterInfo.cpp

[Duncan Sands]

Hi,

> >> The separation of the EH table and frame move data is,
> >> I think, logically figured out, but either one still
> >> causes full EH info to be generated (not sure how to
> >> split the metadata correctly).
> >
> > Me neither, but it would be a nice win if we could.  Want
> > to open a PR for this?
> 
> I'm not sure it's even possible on Darwin; our linker has a fair  
> amount of
> knowledge about EH tables built into it, and may not take kindly to  
> having them change.
> There is also the matter of binary compatibility with gcc-compiled code.

it should be pretty easy to generate a frame moves entry with no
actual moves in it, just the surrounding junk.  This should be
compatible with anything.  I've opened PR2188 for this.  That said,
you already dealt with the most important case - while it would be
nice to go all the way, PR2188 won't make a difference most of the
time.

Ciao,

Duncan.