[LLVMdev] [PATCH] Go on dragonegg

[Duncan Sands]

Hi Sanjoy,

>> I think the right approach is to add an llvm.adjust.trampoline intrinsic
>> to LLVM (and change llvm.init.trampoline to not return a result).  Then the
>
> Won't that break previous code that relies on the current
> llvm.init.trampoline? I can start work on this if that is not a problem.

the usual way of handling this kind of thing is using auto-upgrade
(see llvm/AutoUpgrade.h).  When the old llvm.init.trampoline intrinsic is
seen, it can be replaced by a call to the new llvm.init.trampoline intrinsic
followed by a call to llvm.adjust.trampoline.  So while, yes, this is an
issue that needs to be dealt with, it should be easily taken care of thanks
to the auto-upgrade infrastructure.

Thanks for working on this!

Ciao, Duncan.