similar to: JITted code and thread-local storage

I had tried this in https://reviews.llvm.org/D8815, but we've since switched to a home grown TLS implementation, so I currently don't have a need for this. On Thu, Aug 18, 2016 at 12:17 AM, Alex Denisov via llvm-dev < llvm-dev at lists.llvm.org> wrote: > /cc Lang Hames > > > On 17 Aug 2016, at 19:27, Antoine Pitrou via llvm-dev < > llvm-dev at lists.llvm.org>

Hello, I am a bit curious about the rationale for the current callback-based object cache API. For Numba, it would be easier if there would be a simple procedural API: - one method to get a module's compiled object code - one method to load/instantiate a module from a given piece of object code I manage to get around the callback-based API to do what I want, but it's a bit weird to work

Thanks, happy to of confirmed. With that in mind, will use the AST modules provided by the languages (with the exception of libclang for C++). Antoine: Am aware of Numba, nice job there BTW. So is there a [decoupled] LLVM parser which I can use to read Python files and analyse objects (including computing their attributes in OO and setattr scenarios)? On Wed, Jul 1, 2015 at 10:23 PM, Antoine

2016-01-20 1:11 GMT+02:00 Antoine Pitrou via llvm-dev < llvm-dev at lists.llvm.org>: > On Wed, 20 Jan 2016 00:47:56 +0200 > "Eddy B. via llvm-dev" <llvm-dev at lists.llvm.org> wrote: > > > > I would love to know your thoughts on this, and more specifically: > > Which of the 3 (byval(T), byval(N) and byval + dereferenceable + align) > > do you

Hello, I haven't found any relevant info in the docs about this. I'm trying to build LLVM 3.7.1 on OS X but it fails in the configuration phase. Here are the relevant parts of the output: $ cmake -DCMAKE_INSTALL_PREFIX=/Volumes/HD2/jenkins/workspace/LLVMDev/label/osxbuild/miniconda/envs/_build -DCMAKE_BUILD_TYPE=Release -DLLVM_TARGETS_TO_BUILD=host -DLLVM_INCLUDE_TESTS=OFF

Hmm, I'm confused. The DSO is compiled with gcc. Do I need to compile it with clang instead? I don't believe the JITted code uses the thread support library directly, although I suppose it may be hidden with templates and/or inline functions... On Mon, Sep 28, 2020 at 10:43 PM Lang Hames <lhames at gmail.com> wrote: > > Hi Geoff, > > If you want to access the variable

Hello, LTO is currently the only library which is always built as shared, even under Windows. This actually seems to lead to failure using LLVM in another project under Windows, at least for me (the error message complains about "LTO-NOTFOUND.OBJ"). Switching it to a static library fixes the issue (again, at least for me under Windows). The change was made in:

On Thu, 12 May 2016 16:40:44 +0100 David Chisnall via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > The end result is that shortly after a release (sometimes every alternate release) is branched a load of downstream projects update to the new APIs, test things, and find a bunch of regressions that have been sitting in the tree for months. We then have to scrabble to bisect and try

On Tue, Feb 17, 2015 at 8:56 AM, Antoine Pitrou <antoine at python.org> wrote: > > Hi, > > Dirkjan Ochtman <dirkjan <at> ochtman.nl> writes: > > > > As far as I understand, this change is wanted because the LLVM > > infrastructure derives no value from knowing the types, and there's a > > cost in terms of code spent to support all of it.

Yep we have our own parser <https://github.com/vinzenz/libpypa/> and we would love to see other people use it. When we looked around at some other Python parsers we didn't feel like any of them were easy to extract and use on their own, so we wrote our own and I think were able to keep ours well-separated. There are some things that make parsing Python somewhat difficult to do in a

Hi, On Thu, 28 Jul 2016 09:32:18 -0700 Reid Kleckner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I think David and I are probably the most familiar with how WinEH works in > LLVM, but I don't think either of us has time to prepare a talk for the dev > meeting. I'm trying to prepare a talk on supporting the MS debug info > format in LLVM this year. That said,

On Tue, 11 Oct 2016 13:46:35 -0700 Michael Kuperstein via llvm-dev <llvm-dev at lists.llvm.org> wrote: > To the best of my understanding - because we want to be able to bootstrap > clang with the system compiler that ships with various linux and BSD > distributions. > Windows has no equivalent concept. To elaborate on this: if you want to produce binaries compatible with old

I don't think it's especially hard, but just not specifically unimplemented because nobody's had a strong need for it. There's probably some combinations of code models and machines that does happen to work (e.g. emutls+linux+large-code+large-data+no-PIC). Julia has some support for thread locals, but as a JIT in control of the language we currently try to generate better code than

> On Jan 12, 2017, at 5:03 AM, Antoine Pitrou via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Mon, 9 Jan 2017 11:43:17 -0600 > Wei Ding via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> Hi, >> >> I want an efficient way to implement function pow in LLVM instead of >> invoking pow() math built-in. For algorithm part, I am clear for the

This had also came up at llvm-devmtg briefly at the JIT roundtable. One of the collaborators on my project had started a patch years ago to implement some of it https://reviews.llvm.org/D8815, but then we went a different direction with TLS in our frontend and it became unnecessary. On Fri, Dec 20, 2019 at 12:36 PM David Blaikie via llvm-dev < llvm-dev at lists.llvm.org> wrote: > +Lang

IIRC when LLVM came out a bunch of community-contributed parsers were available on your website. Essentially I want to read in a programming language, prune the AST until it contains only what I define as a "summary", then convert that AST to that of another language, before finally outputting [code-generating] a compilable/interpretable source [think boilerplate]. Would be good to

Hello, With LLVM 3.7.1 on target triple 'x86_64-unknown-linux-gnu', I'm trying to use the "@llvm.canonicalize.f64" intrinsic and I get the following error: LLVM ERROR: Cannot select: intrinsic %llvm.canonicalize Is this a known issue? I tried the equivalent formulations listed in the language reference (such as addition with -0.0 or multiplication with 1.0) but those are

On Tue, 04 Oct 2016 15:29:14 +0000 Zachary Turner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I'm not familiar with the release process, but couldn't most of the > concerns raised in this thread be addressed by shipping prebuilt binaries > for these big platforms with older toolchains? That wouldn't address the cases where people use different build options (e.g.

Hi there, Sorry, I don't have the thread history to reply to since I normally read llvmdev through the archives, but wanted to give my .02 of feedback anyway. As far as I understand, this change is wanted because the LLVM infrastructure derives no value from knowing the types, and there's a cost in terms of code spent to support all of it. I've been creating a frontend that mostly

> On Jan 12, 2017, at 12:58 PM, Friedman, Eli via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 1/12/2017 9:33 AM, Mehdi Amini via llvm-dev wrote: >>> On Jan 12, 2017, at 5:03 AM, Antoine Pitrou via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>> On Mon, 9 Jan 2017 11:43:17 -0600 >>> Wei Ding via llvm-dev <llvm-dev at