Hello, I've recently finished moving a cross-platform project to LLVM 3.0 and now transitioning to 3.1. One of the things I've hit is on OS X, I have linker errors involving JITEventListener and I've noticed if I move the JITEventListener destructor out of JIT.cpp and into JITEventListener.h (like other functions of JITEventListener), the linker is much happier. I'd like to push this change back to LLVM trunk if people think it is good. What do I need to do to gain blessings and permission to do this? Aaron Dwyer Imagination Technologies -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120524/dae8068e/attachment.html>
Aaron Dwyer <Aaron.Dwyer at imgtec.com> writes:> I've recently finished moving a cross-platform project to LLVM 3.0 and > now transitioning to 3.1. One of the things I've hit is on OS X, I > have linker errors involving JITEventListener and I've noticed if I > move the JITEventListener destructor out of JIT.cpp and into > JITEventListener.h (like other functions of JITEventListener), the > linker is much happier. I'd like to push this change back to LLVM > trunk if people think it is good. What do I need to do to gain > blessings and permission to do this?Just post the explanation and the patch on the llvm-commits mailing list.
Possibly Parallel Threads
- [LLVMdev] [llvm-commits] JITEventListener for eventual profiling and maybe gdb support
- [LLVMdev] [llvm-commits] JITEventListener for eventual profiling and maybe gdb support
- [LLVMdev] JITEventListener for eventual profiling and maybe gdb support
- [LLVMdev] JITEventListener for eventual profiling and maybe gdb support
- Interest in integrating a linux perf JITEventListener?