similar to: I've seen OrcJit is under overhaul, and also the MCJIT, so what's the plan?

+ MLIR dev mailing list since that’s where the OrcJit I’m using is. Thanks for all the details, Lang! What you described is exactly what I’m looking for! Please, MLIR dev, let me know if this debug feature and the solution that Lang describes below is interesting for MLIR. I’ll dig more into the details then but it doesn’t seem too complicated. Thanks, Diego From: Lang Hames [mailto:lhames at

Hello, I was wondering if there is someone already working on putting the new OrcJIT APIs in the LLVM-C bindings? Also, is there a general consensus to also add C bindings when new major features are added? Hayden -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150201/061f5949/attachment.html>

Hi Stefan Thank you! In case, you missed in llvm-dev listing: you can find the proposal here : link. <https://docs.google.com/document/d/1202EcXlWMQ8yxu5qD0b5fE0a_kihlcaPNpZo_Jk0YeQ/edit?usp=sharing> Thanks for working on summarising the Bugzilla tickets to track the recent changes in ORC this is really helpful. On Sat, 18 May 2019 at 21:33, Stefan Gränitz <stefan.graenitz at

We are trying to switch to the new orc v2 lljit engine at my work with hopes of parallel jitting. We are switching from the ExecutionEngine w/ OrcMCJitReplacement. We are having a hard time with global variables. We have found a way to create/emit new globals during jitting by using the old ExecutionEngine::getOrEmitGlobalVariable. Is there an easier way to do this with the new jit engine? We were

Hello LLVM developers, I am developing a small project using LLVM. The objective is to provide dynamic loading via JIT compilation of C++ code contained in a (TS) module. For this reason, I would like to return an explicitly raw void pointer (resembling libdl's `void *dlsym(void *, char const *);` as closely as possible) to the compiled result. The MCJIT class offers the most convenient API

I looked around for the status of OrcJIT FFI support. The last e-mail thread I could find was this one: Link <http://lists.llvm.org/pipermail/llvm-dev/2015-February/081679.html> Raw: http://lists.llvm.org/pipermail/llvm-dev/2015-February/081679.html Is OrcJIT now considered stable enough that there can be "official" exposed C APIs? If not, what's the standard approach if I

For example, ELF.h MachO.h and COFF.h should moved into Object directory with new name. and Dwarf.h should moved into DebugInfo directory. 2013/6/29 Eric Christopher <echristo at gmail.com>: > Where would you like to move them? > > -eric > > On Fri, Jun 28, 2013 at 10:38 AM, 罗勇刚(Yonggang Luo) > <luoyonggang at gmail.com> wrote: >> From my point of view, the

Hi, I intend to participate in Google's Summer of Code this year, so I'd like to bounce another idea around to see what you guys think. (I posted a similar message to cfe-dev just now.) Be warned: this will shock you. It may even horrify you. 1. Implement a 16-bit x86 backend. (*Chris recoils in horror*) Yeah, I know 16-bit x86 is dead, but I find it interesting for historical purposes

>From my point of view, the Support library should be more pure. And should not contains too much LLVM-related APIs and defines, -- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo

Well, is that possible to include libstdc++4.7 into llvm? On Wed, Jun 29, 2016 at 2:26 AM, Brian Cain <brian.cain at gmail.com> wrote: > Sorry if I was unclear, I have no problems building clang against a newer > gcc for my own purpose. But it doesn't make sense to provide a release > binary for clang that's hosted on llvm.org that's ostensibly for >

Going to be interesting layering issues if you do the latter. Then you have CodeGen depending upon DebugInfo instead of just a header in Support. -eric On Fri, Jun 28, 2013 at 11:08 AM, 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com> wrote: > For example, > ELF.h MachO.h and COFF.h > should moved into Object directory with new name. > and Dwarf.h should moved into DebugInfo

It is possible to statically link against libstdc++, yes. I don't quite know all the pieces to the recipe in order to get that to work. It would require changes to the release script in order to get those configuration changes all the way through the third phase build. I don't believe any other tarball release does this, so it would at least be an unconventional release. On Wed, Jun

-- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161115/80fd3c17/attachment.html>

2013/10/19 Rafael Espíndola <rafael.espindola at gmail.com>: > On 19 October 2013 06:01, 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com> wrote: >> I found that access llvm-mc from clang driver is impossible, and I >> want to use llvm-mc to compile assembly files, how to do that? > > Try "clang -integrated-as -c test.s" Thank you very much, I use the

I've been playing with OrcJIT a bit, and from the looks of it I can (like in the previous JIT I suppose?) ask for a function to be re generated. If I've given the address of the function that LLVM gave me to an external party, do "I" need to ensure thread-safety? Or is it safe to ask OrcJIT to re generate code at that address and everything will work magically? I'm

Hi All, I'm back again after a couple of weeks hiatus, and I have some good news for anyone interested in cross-process JITing with OrcV2: The remote TargetProcessControl and Orc library breakup patch has landed in 1d0676b54c4 [1]. Thanks very much to Dave Blaikie and Stefan Graenitz for all their feedback on the review! As described in my last email, this commit breaks the OrcJIT library

[root at localhost clang+llvm-3.8.0-linux-x86_64-centos6]# cd bin [root at localhost bin]# ./clang ./clang: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by ./clang) ./clang: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./clang) ./clang: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.14' not found (required by ./clang) ./clang: /usr/lib64/libstdc++.so.6:

Hell, Brian, I found a way to install Gcc 5.3 on CentOS 6 without the need to building it from source. You may try it on CentOS 6.0 That's makes clang/llvm won't depends on the newer version of glibc 2.14 The instruction: vim /etc/yum.repos.d/llvm.repo The content: ``` [sclo] name=SCLO baseurl=http://mirror.centos.org/centos/6/sclo/x86_64/rh/ gpgcheck=0 enabled=1 ``` Installation step:

Cause llvm-libc are in early stage, and we can easily catch up the support with linux. After we add wasi support in llvm-lic, we can easily get a usable llvm-libc across different platform such as linux/windows/macos/android. don't know if iOS is a target, but these target are very much enough -- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo -------------- next part -------------- An

I means visual studio c++ 2008, do you build clang+llvm with .sln files, and these files are generated by cmake? I do of that. And because vs c++ can't recognize path such a:/filepath/.. Properlyn it's recognized as a:/filepath So we need change /.. to /../ or /../. 2009/8/6, Daniel Dunbar <daniel at zuster.org>: > I don't understand this problem, I have built clang on