similar to: LLJVM make error

That source file was removed from LLVM in r232397 on March 16, 2015. It looks like lljvm hasn't been updated in a long time. LLVM's C++ APIs are not stable, so there is no expectation that a project built against LLVM's C++ API in 2015 would build or reasonably function against LLVM trunk. The project probably works against LLVM 3.6.2 which was (I believe) the last LLVM release to

Hi Philip, I also tried that including file: #include "llvm/IR/LegacyPassManager.h" but error remain same. Please help. On Tue, Aug 14, 2018, 2:58 AM Philip Pfaffe <philip.pfaffe at gmail.com> wrote: > Hi Ratnesh, > > the PassManager used in that example has moved into the legacy namespace: > http://llvm.org/doxygen/classllvm_1_1legacy_1_1PassManager.html > >

Hi fellow devs, I was looking for a way to run C on the JVM and i found LLJVM which apparently does exactly that! Howevere,unfortunately it seems dead on the main david's git https://github.com/davidar/lljvm as well as the slightly newer one https://github.com/hyc/lljvm. They don't seem to compile, once i run make in the root directory it give me the error : " *In file included

Hi, I am begineer to llvm, implementing a main.cpp from https://github.com/davidar/lljvm/blob/master/backend/main.cpp A) : When I am declaring a command: * PassManager PM* * PM.add(new DataLayout td)* It shows error: > *error: missing template arguments before ‘PM’* * PassManager PM;* ^ >*main_test.cpp:48:2: error: ‘PM’ was not declared in this scope* *

I am following the code of the project https://llvm.org/svn/llvm-project/java/trunk/lib/Compiler/Resolver.cpp, But some class/function of it is not present in my source code due to replacement of this function in newer llvm verion. Can someone please suggest me the alternative approach of these function in latest llvm version. Here are those classes and functions : 1) PATypeHolder 2)

Hi, I have a question regarding PGO. I collected profile data with the instrumentation build (-fprofile-instr-generate) and provided for PGO optimization in the second build (with -fprofile-instr-use=xxx.profdata). This works fine. Then I tried to provide the profile data to opt using the option -pgo-instr-use, but this causes an error with the message: "Not an IR level instrumentation

Hi, I've written a backend for LLVM that allows LLVM IR to be transformed to a Java/JVM class file (llvm-jvm.patch.gz attached). Indirect function calls don't work yet, and there's probably some minor bugs in it, but it works well for the test cases that I've run through it. Also, several instructions are emulated by method calls due to deficiencies in the JVM instruction set

> If you apply that as a patch now, everyone else will have to maintain > it when they do their unrelated changes, increasing the cost of the > project's maintenance. I welcome your code (have been wondering about > it recently too), but I think that you should keep it as a separate > project for now. Once it's at least complete, I'm sure people will be > happy to

My idea was to create a complete backend treating Java as a normal platform, to enable LLVM to compile programs to Java Bytecode (.class) and Java Archive files (.jar). This could be useful in situations where we need to compile a program for a platform still not natively supported by LLVM. I don't know if it exists already, I've heard about this "LLJVM" but I don't think it

Hello, David First of all, thanks for the backend submission. I let Chris comment about the procedure of adding it to the tree. :) I just did a quick look into the code. The comments are below > Indirect function calls don't work yet, and there's probably some > minor bugs in it, but it works well for the test cases that I've run > through it. Could you please provide some

Hello everyone, I am able to work very well with annotations in C/C++, by using __attribute__((annotate("MYANNOTATION"))) static int a; . Inside the LLVM bytecode I have @llvm.global.annotations and @llvm.var.annotation. However, I was trying to test annotations also in Java, with VMKit. These are the commands that I run: javac -Xlint -g -O Main.java ../Release+Asserts/bin/vmjc Main

Hello Harris, Thank you for your answer. So it is there a way of annotating variables in Java Code, so I can see them into LLVM bytecode? Thank you ! On Mon, Jun 17, 2013 at 3:54 PM, Harris BAKIRAS <h.bakiras at gmail.com> wrote: > Hello Alexandru, > > No you did nothing wrong. > > We are using our own data structure to describe annotations in J3. So it > is normal

Hello Alexandru, No you did nothing wrong. We are using our own data structure to describe annotations in J3. So it is normal that you can not see your Java annotations inside the LLVM bytecode produced. If I remember well, our implementation of annotations do not rely on LLVM annotations. Regards, Harris Bakiras On 06/17/2013 02:19 PM, Alexandru Ionut Diaconescu wrote: > Hello

What classpath implementation are you using ? GNUClasspath or OpenJDK ? Harris Bakiras On 06/17/2013 03:57 PM, Alexandru Ionut Diaconescu wrote: > Hello Harris, > > Thank you for your answer. So it is there a way of annotating > variables in Java Code, so I can see them into LLVM bytecode? > > Thank you ! > > > On Mon, Jun 17, 2013 at 3:54 PM, Harris BAKIRAS

Hi, I wanted to use VMKit project to convert Java Bytecode to LLVM IR bitcode. But I do not know how to start, since I came to know that VMkit is written for llvm -3.3 version, but I want it for latest LLVM version 6.0.1. So, could you please suggest me, whether I have to write it whole project from scratch to meet my requirement of latest llvm version, or can use existing project by building

I have code that uses OpaqueType::get(), it was used to be in llvm/IR/DerivedType.h , but it is removed now. What should I use for it replacement. Also, it is using #include <llvm/Bytecode/WriteBytecodePass.h> , but I do not found any WriteBytecodePass.h in my source code. Please tell me, what should I use in replacement of these. Thanks& Regards, Ratnesh Tiwari -------------- next

2009/11/30 David Roberts <d at vidr.cc>: >> Nobody is asking for perfection, just completeness. > I'd just like to point out that I don't have a great deal of > experience in compiler development - I just thought that this would be > an interesting project to try. I realise that it isn't complete in > it's current state. Hi David and Jon, After reading

> Could you please provide some sort of "feature" test? So, we might be > sure that the stuff won't be broken due to e.g. some API change, etc. > Now we have a powerful FileCheck facility, so, you might just have a > one .ll file and check for the JVM code emitted. Additional patch attached, is this suitable? >> In order to link and run the output, the LLJVM[1]

>> > So it will stack overflow on tail calls >> >> At the moment, yes. But then again, so does java. > > Sure but a lot of people like me are using LLVM precisely because it offers > these wonderful features. As long as your JVM backend does not handle these > features correctly its utility is greatly diminished. The issue is that current JVMs don't provide

Hi, David Chisnall via llvm-dev wrote: > On 19 Jul 2016, at 04:06, Lorenzo Laneve via llvm-dev<llvm-dev at lists.llvm.org> wrote: >> My idea was to create a complete backend treating Java as a normal platform, to enable LLVM to compile programs to Java Bytecode (.class) and Java Archive files (.jar). This could be useful in situations where we need to compile a program for a