search for: llvmlite

​Hi all, I am using llvmlite for pyvex and I want the output of my code (which is written based on llvmlite) to be like pyvex. In pyvex, (https://github.com/angr/pyvex). Considering pyvex, I tried to implement the following statements in pyvex to llvmlite: for stmt in irsb.statements: if isinstance(stmt, pyvex.IRStmt.Store):...

Hello, We are happy to release version 0.10.0 of llvmlite. llvmlite is a light-weight Python binding for LLVM (compatible with Python 2.7 as well as Python 3.4 and later). It stems from the needs of the Numba community and is geared towards creating JIT compilers. llvmlite is available both as source code and as binaries for a number of platforms. Sou...

...vm-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 think would provide the easiest transition path for front-ends? > > We (llvmlite and Numba) don't use byval specifically but, were we to use > it, I think byval(T) would by far be the easiest for us. By contrast, > computing ABI sizes is a bit of a PITA due to llvmlite's architecture > (llvmlite's IR generation side doesn't call into LLVM at all, it &g...

Hi, I wrote yet another [1,2] Python binding for LLVM! I'm doing this because llvmlite has some serious limitations: 1) it cannot parse an existing IR, only create new modules [3], 2) it keeps its own representation of the IR (which is less memory efficient than the LLVM one), and 3) each llvmlite version supports a single LLVM version. Considering that my need is to load modules of...

There is llvmlite http://llvmlite.readthedocs.io/en/latest/ , but it doesn't seem to support reading individual instructions, based on these docs. I was thinking to make a simple code analysis tool to, for example, find all system calls that have unchecked return codes, but I can't find a binding for a...

​Hello all, I have written a code in llvmlite. Using command numba --dump-llvm example.py > example.ll I can have .ll file. However, using lli example.ll, I am stopped with error: 'main' function not found in module. Is there anyway at which it can be executed using lli? Thank you in advance Best -- This email was Anti Virus...

...Is? Otherwise this makes debugging significantly > > harder for me. I've also really liked how readable LLVM IR is, and it > > would seem like this change would negatively affect the readability. > > I kindof agree with Dirkjan. We use a similar approach (Numba calls into > llvmlite to generate textual LLVM IR), and the type checking can come in > handy to avoid later crashes (otherwise it's very easy to mess up a > getelementptr instruction). > > However, llvmlite does track types on its own, so we could also add our > own error checking before generating t...

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

...mming language, entirely written in Python. I state that I work under Windows, I'm using anaconda and Python 3.6. I wrote the lexical generator and the parser generator. Now I have to write a code generator and thought about using LLVM. It seems that the Uncio way to work with LLVM in Python is llvmlite, necessary to generate the code. Then I have to use LLC. exe and clang. EXE to compile the generated code into an executable. Since I would like to distribute this language, I want to know: I must include all the installation of LLVM, or can I use its libraries to generate the code and compile i...

...have been sitting in the tree for months. We then have to scrabble to bisect and try to track them down. > > TL;DR version: If we want downstream people to test ToT, then we need to make updating LLVM library consumers to ToT far less painful than it is now. +1 to this. As a developer of llvmlite and numba, it would be counter-productive for me to try to follow the LLVM ToT, as opposed to migrate after a X.Y.1 release as we currently do. Regards Antoine.

...the slides from my lowRISC talk here](https://speakerdeck.com/asb/lowrisc-the-path-to-an-open-source-soc). If you want to chat about the project, you may want to join #lowRISC on irc.oftc.net. ## News and articles from around the web Eli Bendersky has written a useful [introduction to using the llvmlite Python to LLVM binding](http://eli.thegreenplace.net/2015/building-and-using-llvmlite-a-basic-example/), which was borne out of the Numba project. LLVM/Clang 3.6-rc2 [has been tagged](http://article.gmane.org/gmane.comp.compilers.llvm.devel/81600) and is ready for testing. The next LLVM bay-area...

Hi Yuri, When you say code analysis, do you mean checking from source code itself, the intermediate representation, the assembly instructions or the binary? Brenda On Mon, Jan 1, 2018 at 1:26 AM, Yuri via llvm-dev <llvm-dev at lists.llvm.org> wrote: > There is llvmlite http://llvmlite.readthedocs.io/en/latest/ , but it > doesn't seem to support reading individual instructions, based on these > docs. > > > I was thinking to make a simple code analysis tool to, for example, find > all system calls that have unchecked return codes, but I can...

Hi, I've recently run into a problem of missing !dbg metadata after the code has been optimized (even opt -O1). The original code was generated using llvmlite python package and I've verified that all instructions have their !dbg metadata present. After optimizing the module (even opt -O1) I see that some instructions (~25%) don't have any dbg metadata. These are mostly getelementptr and bitcasts, but there's also few fsubs. One example: %....

...lt;unlurking> Is it? If you pass an invalid fd to the libc, it replies with a EBADF, it doesn't crash hard. Most mature libraries have guards against invalid or inconsistent parameter values, and return error codes to the caller. As someone who maintains and uses an LLVM binding to Python (llvmlite), it's one of the annoyances we have faced: if someone makes a mistake when calling one of the exposed APIs, that API may crash the process (while, as Python programmers, they would rather get an exception, which at least makes it easier to debug and diagnose the issue). Getting a crude assert-...

Hi, In the past months, several options have been presented for making byval (and similar attributes, such as inalloca or sret) work with opaque pointers. The main two I've seen were byval(T) and byval(N) where N is the size of T. They both have their upsides and downsides, for example: byval(T) would be a type-parametric attribute, which, AFAIK, does not already exist and may complicate

Hal Finkel <hfinkel <at> anl.gov> writes: > > Do you require long-term cross-release ABI and/or API stability > from the C API that you're using? Do these > other projects? For the record, in llvmlite and Numba we don't require C API stability for two reasons: 1) the C API is not enough for us and we rely on bits of the C++ API 2) we also rely on other details such as textual IR format, which change from release to release anyway. Regards Antoine.

On 12 May 2016 at 16:56, Kristof Beyls <Kristof.Beyls at arm.com> wrote: > In my opinion, it would be better overall for the LLVM project if > top-of-trunk is > tested as much as possible, if testing resources are so scarce that a > choice > has to be made between testing top-of-trunk or testing a release branch. > I agree that trunk is more important, with both of my

> On Feb 16, 2016, at 1:14 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > > On 15 Feb 2016, at 23:12, Andrew Trick via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Prior to FTL, JavaScriptCore had no dependence on the LLVM project. Maintaining a dependence on an external project naturally has integration overhead. > > And the fact that

On Sat, Dec 17, 2016 at 9:32 PM, Sean Silva via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Fri, Dec 16, 2016 at 12:31 PM, Pete Cooper via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> >> On Dec 16, 2016, at 11:46 AM, Rui Ueyama <ruiu at google.com> wrote: >> >> On Fri, Dec 16, 2016 at 11:18 AM, Pete Cooper

----- Original Message ----- > From: "Hayden Livingston" <halivingston at gmail.com> > To: "Eric Christopher" <echristo at gmail.com> > Cc: "Chris Lattner" <clattner at apple.com>, "Hal Finkel" <hfinkel at anl.gov>, "LLVM Dev" <llvmdev at cs.uiuc.edu>, "Lang > Hames" <lhames at apple.com>