similar to: [LLVMdev] MSIL and MIPS backend for LLVM

Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] MSIL and MIPS backend for LLVM"

2008 Nov 05
3
[LLVMdev] MSIL and MIPS backend for LLVM
Hi, The code that I was using was this: http://shootout.alioth.debian.org/u32q/benchmark.php?test=nbody&lang=gcc&id=1 I followed the footsteps for compiling it to BC than I took the BC code and compiled it with ilasm2 (Mono). After that I tried to run the .exe with mono and it gave me a invalid opcode. I wish I could give more information about the bug but my ext3fs partition crashed
2008 Nov 05
0
[LLVMdev] MSIL and MIPS backend for LLVM
Hi Eduardo, > I'm a little new to LLVM. > I know that the backends are still in experimental stage. MSIL and MIPS > would be very useful for a project that I'm working on. Do you have any > plans to have it completed in the next few months? I could generate the > MSIL assembly but when compiled it, which compiles sucessfully, it > generates invalid opcode errors. As
2008 Nov 05
0
[LLVMdev] MSIL and MIPS backend for LLVM
Hi On Wed, Nov 5, 2008 at 3:24 PM, Eduardo Augusto Peixoto da Silva Brito <pg12188 at alunos.uminho.pt> wrote: > Hi, > > The code that I was using was this: > http://shootout.alioth.debian.org/u32q/benchmark.php?test=nbody&lang=gcc&id=1 > > I followed the footsteps for compiling it to BC than I took the BC code and > compiled it with ilasm2 (Mono). > After
2008 Nov 05
2
[LLVMdev] MSIL and MIPS backend for LLVM
> Ok, I'll wait for a more detailed description > You can report directly at http://www.llvm.org/bugs/ This seems to be MSIL related, not MIPS. I don't think anyone will be interested in fixing problems of this backend -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University
2008 Nov 05
0
[LLVMdev] MSIL and MIPS backend for LLVM
On Wed, Nov 5, 2008 at 4:13 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> Ok, I'll wait for a more detailed description >> You can report directly at http://www.llvm.org/bugs/ > This seems to be MSIL related, not MIPS. I don't think anyone will be > interested in fixing problems of this backend oops! :) -- Bruno Cardoso Lopes
2008 Nov 05
1
[LLVMdev] MSIL and MIPS backend for LLVM
Both backends are important but I find it more important the MSIL backend, for now. It's a shame that nobody is picking up the MSIL backend; it would be useful another backend that is machine-independent and that has support for several tools. -----Mensagem original----- De: llvmdev-bounces at cs.uiuc.edu em nome de Bruno Cardoso Lopes Enviada: qua 05-11-2008 19:47 Para: LLVM Developers
2012 Dec 27
2
[LLVMdev] llvm msil couple questions
Hey there, Searching via the web is not producing answers.... So I thought I would ask the gods of llvm. :-) I'd like to experiment with the llc in conjunction with msil. but I am running into this error: llc-mp-2.9 test.ll -march=msil /opt/local/libexec/llvm-2.9/bin/llc: error: invalid target 'msil'. the version string is: llc-mp-2.9 --version Low Level Virtual Machine
2009 May 16
2
[LLVMdev] VMKit: msil optimization
Hello all. is it possible to use LLVM to optimize existing .NET assemblies? Basically doing the following: - read in MSIL and convert into LLVM internal representation - perform global optimizations on LLVM internal representation - write out optimized MSIL using the existing LLVM backend I presume that the capability to convert MSIL into LLVM internal representation exists somewhere in VMKit.
2009 May 16
2
[LLVMdev] VMKit: msil optimization
Hello, > As for the state of the MSIL backend of LLVM, I don't think it's for > production use yet. Assemblies have lots of information in them and > maintaining them during the MSIL -> LLVM -> MSIL translations should be > the hard part. This should be pretty hard. MSIL is definitely much more high level than LLVM, that's why significant portion of information will
2009 Mar 30
2
[LLVMdev] MSIL codegen
Hello, I work in Kalray (Montbonnot, France) and I'm PhD student at Universite Joseph Fourier in Grenoble. We want to use LLVM framework for MSIL code generation, which is part of my thesis. Currently I'm still reading LLVM's documentation and I've started completing the MSIL backend for running on Mono. Things that need to be fixed include pointers initialization, call to
2009 Mar 30
0
[LLVMdev] MSIL codegen
Hi Artur, Artur Pietrek wrote: > Hello, > > I work in Kalray (Montbonnot, France) and I'm PhD student at Universite > Joseph Fourier in Grenoble. > We want to use LLVM framework for MSIL code generation, which is part of > my thesis. > Currently I'm still reading LLVM's documentation and I've started > completing the MSIL backend for running on Mono.
2009 May 16
0
[LLVMdev] VMKit: msil optimization
Dear Rudiger, RĂ¼diger Klaehn wrote: > Hello all. > > is it possible to use LLVM to optimize existing .NET assemblies? > It's in theory possible. LLVM+VMKit already does it for Java classes. > Basically doing the following: > > - read in MSIL and convert into LLVM internal representation > - perform global optimizations on LLVM internal representation > - write
2007 Mar 22
1
[LLVMdev] MSIL backend
Hello, Jeff. > I'm confused. A MSIL front end I can understand, but a back end? How > will it be used? The GCC-based front ends that come with LLVM generate > bytecodes that have dependencies on the GCC runtime, which is not going > to be present in a .NET environment. Well. It's LLVM-to-MSIL translator. So, if the source use some unsupported code... The same situation
2007 Mar 21
4
[LLVMdev] MSIL backend
Hello, Everyone. We've just commited new backend for LLVM: MSIL. The author of backend is Roman Samoilov from Codedgers Inc. (roman at codedgers.com). Backend itself is very similar to C backend (and actually was based on it). Note, it's pure LLVM-to-MSIL translator, so no additional checks etc. are performed. Backend is usable in general, but still lacks some important features: 1.
2007 Mar 23
1
[LLVMdev] MSIL backend
On Thu, 22 Mar 2007, Jeff Cohen wrote: > The problem is worse than I thought. > > MSIL, and .NET in general, defines a specific object model. This object > model is explicitly part of MSIL semantics. LLVM is at a lower level; > it does not have an object model. To do a virtual call, LLVM > instructions must be generated to load a function pointer from a vtable Unlike Java,
2007 Mar 22
0
[LLVMdev] MSIL backend
Hello, Jeff. > and dereference it. But MSIL is at a higher level, where one simply > uses the callvirt instruction to do a virtual call and no vtable is > supplied or even present. You're right. Consider we will have some FE for MSIL, which will just generate LLVM's "call" instruction with some predefined CC, which will mean "this is virtual call". Backend
2007 Mar 22
0
[LLVMdev] MSIL backend
Chris Lattner wrote: > On Thu, 22 Mar 2007, Jeff Cohen wrote: >> I'm confused. A MSIL front end I can understand, but a back end? How >> will it be used? The GCC-based front ends that come with LLVM generate >> bytecodes that have dependencies on the GCC runtime, which is not going >> to be present in a .NET environment. > > Who said the input has to come
2007 Mar 22
3
[LLVMdev] MSIL backend
On Thu, 22 Mar 2007, Jeff Cohen wrote: > I'm confused. A MSIL front end I can understand, but a back end? How > will it be used? The GCC-based front ends that come with LLVM generate > bytecodes that have dependencies on the GCC runtime, which is not going > to be present in a .NET environment. Who said the input has to come through the GCC front-ends? Perhaps this is for
2008 May 06
1
[LLVMdev] Problem about "llc -march=msil"
Hi, I am trying to use llvm to translate ftp.c(a file of wget-1.11.2.tar.bz2 ) to msil. But it shows errors like: [dayin at localhost src]$ llvm-gcc -emit-llvm ftp.c -c -o ftp.bc [dayin at localhost src]$ llc ftp.bc -march=msil -o ftp.s Intrinsic ID = 32 llc: /home/dayin/llvm/llvm-2.2/lib/Target/MSIL/MSILWriter.cpp:802: void <unnamed>::MSILWriter::printIntrinsicCall(const
2009 May 16
0
[LLVMdev] VMKit: msil optimization
On Sat, May 16, 2009 at 5:09 PM, Anton Korobeynikov <anton at korobeynikov.info > wrote: > Hello, > > > As for the state of the MSIL backend of LLVM, I don't think it's for > > production use yet. Assemblies have lots of information in them and > > maintaining them during the MSIL -> LLVM -> MSIL translations should be > > the hard part. > This