Displaying 20 results from an estimated 105 matches for "aoted".
Did you mean:
noted
2005 Nov 28
2
[LLVMdev] Help setting up a llvm project
First I'd like to let you know I've started working on porting gcjx to llvm.
Some other intrested people may help but I've just started the project.
My first question is I'm porting gcjx over to use the llvm build
system I've successfully created a number of libraries but gcjx uses a
number of sub directories for its source and I'd like the .o files for
all of them to
2005 Nov 28
0
[LLVMdev] Help setting up a llvm project
Hi Mike,
Sounds like an interesting project. Here's some ideas for you on the LLVM
Makefile System.
If you haven't, I *strongly* suggest you read the makefile and project
documentation (docs/MakefileGuide.html and docs/Projects.html). There is much
information there that you need to understand.
LLVM is set up so that a single directory builds a single result. Since your
source code
2010 Jul 16
1
[LLVMdev] java front-end
Hi Minas,
Thanks! I wasn't aware that VMKit had the ability to generate llvm code
from .class / .jar files - I thought all of its code-generation capabilities
were very closely tied to the VM itself. I'll look into this.
The motivation behind this project is to be able to get both the small size
and fast startup times of Avian, along with the speed of llvm-generated
code.
Currently,
2010 Jul 16
0
[LLVMdev] java front-end
Hi Joshua,
> I'm trying to use the Java front-end (which, based on svn commits, appears
> to be three-years-dead),
> I'm trying to use llvm as a replacement aot compiler
I'm not acquainted with the Avian JVM, but
haven't you considered using VMkit llvm project, it contains
.class/.jar to llvm compiler, also JIT compiler(native code compiler)
and aot compiler.
And
2014 Mar 07
2
[LLVMdev] Running VMKit's AOT Java Compiler
Hi,
I'm new to VMKit and I'm trying to use its AOT Java compiler but I'm
immediately getting an error message which I don't understand.
Everything was compiler as suggested in the Getting Started tutorial, using
GNU Classpath. I try to run:
llcj ../../tools/trainer/Release+Asserts/HelloWorld.class
and get the following output:
Can not materiale a function in AOT mode.0
2010 Aug 02
0
[LLVMdev] VMkit AOT build problem: llc crushed on glibj compilation to native(.s) file
On Mon, Jul 19, 2010 at 7:40 PM, Minas Abrahamyan <minas.subs at gmail.com> wrote:
> Trying to build AOT version of vmkit java,
> building for that classpath glibj.zip:
>
> $ cd vmkit/tools/vmjc/libvmjc
> $ make ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1 REQUIRES_FRAME_POINTER=1
>
> has eventually, after 50 minutes, brought:
> <<<
> llvm[0]: Compiling
2010 Jul 19
2
[LLVMdev] VMkit AOT build problem: llc crushed on glibj compilation to native(.s) file
Hi,
Trying to build AOT version of vmkit java,
building for that classpath glibj.zip:
$ cd vmkit/tools/vmjc/libvmjc
$ make ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1 REQUIRES_FRAME_POINTER=1
has eventually, after 50 minutes, brought:
<<<
llvm[0]: Compiling glibj.zip to llvm
llvm[0]: Optimizing glibj.zip
llvm[0]: Compiling glibj.zip.bc to native
UNREACHABLE executed!
0 llc
2010 Jul 16
3
[LLVMdev] java front-end
Hi,
I'm trying to use the Java front-end (which, based on svn commits, appears
to be three-years-dead), and I'm running into some build errors. In that
time did llvm change from building with exception handling and rtti to
building without?
I remember reading somewhere that llvm code should use dyn_cast instead of
dynamic_cast. Do these need to be changed here?
A little background:
2016 Jul 03
2
Status of stack walking in LLVM on Win64?
Hi all,
I'm developing a novel language that has historically used LLVM for code
generation, behind a custom self-hosted front-end. The runtime for this
language offers a garbage collector.
In the past I've been on 32-bit Windows where precise garbage collection is
relatively straightforward (as long as FPO is disabled). Walking the stack
is a simple bit of pointer chasing and some
2012 Jun 28
0
[LLVMdev] A common runtime environment / object model for AOT compiled languages?
Something that I've been pondering for a while: Does the idea of a common
runtime environment & object model for ahead-of-time compiled languages
make sense?
Let me explain what I mean by "runtime environment" - I'm not talking about
a replacement for glibc or anything on that level. Rather, I'm thinking of
something more like Java but without the interpreter or JIT,
2010 Aug 04
0
[LLVMdev] VMkit AOT build problem: llc crushed on glibj compilation to native(.s) file
Well, I think there is a bug in vmkit for always trying to do pointer
arithmetic using i32 instead of the target's pointer size, which is
what my patch addressed.
As for whether there is a bug in LLVM, I'm not sure. I've played
around with it some more, and it looks like zext expressions get
constant folded before reaching LowerConstant. The only way I've
triggered the
2014 Sep 09
2
[LLVMdev] VMKit is retired (but you can help if you want!)
Oups, sorry for the mistake, llcj (not llc:)) is not more maintained!
Gaël
Le 10 sept. 2014 00:27, "Gaël Thomas" <gael.thomas00 at gmail.com> a écrit :
> Hi Brian,
>
> So, I confirm, llc is not more maintained. And using vmjc is probably
> the good starting point to translate Java bytecode into llvm bitcode.
>
> However, I think that your hack (changing the way
2010 Aug 04
1
[LLVMdev] VMkit AOT build problem: llc crushed on glibj compilation to native(.s) file
On Tue, Aug 3, 2010 at 6:50 PM, Allan Tong <actong88 at gmail.com> wrote:
> Is the pointer->i32->pointer case a valid use case? It seems like
> such instances would be errors in the user's code, and that it may not
> be so bad that LLVM will error on them.
It's not usually useful, but it shouldn't be an error; please file.
-Eli
2014 Apr 06
2
[LLVMdev] Using StartJnjvmWithJIT from jnjvm.cpp in VMKit
Hi
Does anybody use *StartJnjvmWithJIT* from jvjvm.cpp in VMKit?
Becuase , I am looking to use without JIT when we are running the Java
byte code. My concern is StartJnjvmWithJIT getting three argument *int
argc, char** argv, char* mainClass* - why we need to pass *argv and
mainclass* arguments here?
please help me on this.
Regards
Sri.
-------------- next part --------------
An
2010 Aug 03
2
[LLVMdev] VMkit AOT build problem: llc crushed on glibj compilation to native(.s) file
Hi Allan,
Thanks for the fix! So is this a bug in LLVM? Can you reduce that to a small
test case and file a bug?
Nicolas
2010/8/2 Allan Tong <actong88 at gmail.com>
> On Mon, Jul 19, 2010 at 7:40 PM, Minas Abrahamyan <minas.subs at gmail.com>
> wrote:
> > Trying to build AOT version of vmkit java,
> > building for that classpath glibj.zip:
> >
> > $ cd
2016 Jul 06
2
Status of stack walking in LLVM on Win64?
Can we accept the patch which makes this work? There is a patch in the
bug report for the MCJIT case. I'm confused why AOT and MCJIT case
would be different but without it the information isn't registered.
On Wed, Jul 6, 2016 at 9:07 AM, Reid Kleckner via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> If you want an AOT linker and you don't want to use link.exe, you can use
2010 Sep 28
1
[LLVMdev] [VMKit-2.7] libvmjc.so building problem
I followed instructions in this page to setup my environment:
http://vmkit.llvm.org/get_started.html
My llvm, llvm-gcc, and vmkit are not SVN version.
All of them are downloaded from this page:
http://llvm.org/releases/download.html#2.7
GNU classpath is downloaded from:
ftp://ftp.gnu.org/gnu/classpath/classpath-0.97.2.tar.gz
PNet & PNetlib are not used because I just want the JVM.
I
2016 Jul 03
2
Status of stack walking in LLVM on Win64?
For JITs it would appear that there is a patch needed for some kind of
relocations.
https://llvm.org/bugs/show_bug.cgi?id=24233
Is the patch really needed? What does it do? I'm not an expert here so asking.
On Sun, Jul 3, 2016 at 2:48 AM, David Majnemer via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
>
> On Sat, Jul 2, 2016 at 5:22 PM, Michael Lewis via llvm-dev
>
2013 Dec 18
2
[LLVMdev] Trying to use patchpoint in MCJIT
Ok I see. Of course, at runtime, it's enough for dynamic linking or for
deoptimization. However, wmkit acts both as a jit and as an aot. For the
aot, it means that I can not use patchpoint and that I should have two
different compilation strategy. It's not so difficult, but in this case, I
can not use patchpoints to generate gc's stackmap for the aot (basically, I
think that I could
2010 Jul 20
0
[LLVMdev] Fwd: Building VMKit
On Tue, Jul 20, 2010 at 5:35 PM, Joshua Warner <joshuawarner32 at gmail.com>wrote:
> Hi Nicolas,
>
> I plan on using the Avian GC (which is a precise, generational collector).
>
OK - Great!
> Eventually, I'd like to fully integrate all of the runtime services Avian
> provides - even integrating the existing Avian JIT compiler, to allow for
> partially-AOT