similar to: [LLVMdev] llvm 2.0 release announcement [draft]

Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] llvm 2.0 release announcement [draft]"

2007 May 14
0
[LLVMdev] llvm 2.0 release announcement [draft]
Chris Lattner wrote: > x. Roman Samoilov contributed a new MSIL backend to LLVM. llc - > march=msil will now turn LLVM into MSIL (".net") bytecode. This is > still fairly early development with a number of limitations. > This ought not be advertised to the world. It is not useful for any purpose. Not only can it not do virtual method calls, as I previously
2007 May 15
1
[LLVMdev] llvm 2.0 release announcement [draft]
On Mon, 14 May 2007, Jeff Cohen wrote: > Chris Lattner wrote: >> x. Roman Samoilov contributed a new MSIL backend to LLVM. llc - >> march=msil will now turn LLVM into MSIL (".net") bytecode. This is still >> fairly early development with a number of limitations. > This ought not be advertised to the world. It is not useful for any purpose. Jeff,
2007 May 23
0
LLVM 2.0 Release
LLVM 2.0 is done! Download it here: http://llvm.org/releases/ or view the release notes: http://llvm.org/releases/2.0/docs/ReleaseNotes.html LLVM 2.0 is a great release in many ways. It includes a wide range of new features, new optimizations, better codegen, and new targets. We were also able to signficantly revise several core aspects of the LLVM IR and design (such as the type system
2007 Feb 26
3
[LLVMdev] another problem with function arguments aligment
The ARM EABI (AAPCS) defines: - i64 values are 8-bytes aligned - "The alignment of an aggregate shall be the alignment of its most-aligned component." So, struct ss { int x; int y; }; void f(int a, struct ss b); r0 <- a r1-r2 <- b void g(int a, long long b); r0 <- a r2-r3 <- b The problem is: llvm-gcc generates the same bytecode for both functions: declare void
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 Feb 09
0
[LLVMdev] problem with function arguments in ARM EABI
I am ok with adding an attribute but don't like to add two of them as you've described. I don't think you need the "sequential piece ID" to deal with this issue, no? You just need a little extra bookkeeping in the target lowering code. Alternatively, you can use a "original alignment" attribute (i.e. alignment of unexpanded argument). That would be a 5-bit
2007 Feb 09
0
[LLVMdev] problem with function arguments in ARM EABI
On Feb 8, 2007, at 10:46 AM, Lauro Ramos Venancio wrote: > I'm facing a problem with functions arguments. ARM EABI defines that > 8-bytes arguments must be 8-bytes aligned. For example: > > void @f(i32 %a, i64 %b) > > ARM EABI: > r0 <- %a > r2,r3 <- %b Ok. I suppose this makes it easier to use 64 bit store instructions. > > Darwin: > r0 <- %a >
2007 Feb 09
2
[LLVMdev] problem with function arguments in ARM EABI
> > Yes, you need to override both LowerArguments and LowerCallTo. All of > the current targets / abi's use the default implementation in > SelectionDAGISel.cpp But I guess ARM EABI will be the first. :-) As > far as I can see, this is the only clean way to do it. I expect the > ARM EABI specific implementation will be quite a bit simpler than the > default implementation
2007 Feb 08
2
[LLVMdev] problem with function arguments in ARM EABI
I'm facing a problem with functions arguments. ARM EABI defines that 8-bytes arguments must be 8-bytes aligned. For example: void @f(i32 %a, i64 %b) ARM EABI: r0 <- %a r2,r3 <- %b Darwin: r0 <- %a r1,r2 <- %b void @g(i32 %a, i32 %b, i32 %c) ARM EABI or Darwin: r0 <- %a r1 <- %b r2 <- %c The problem is: I can't differ a i64 argument of two i32 arguments in
2008 Jan 21
2
[LLVMdev] LLVM build freezes in scratchbox, ARM target
Hi Arvind, To use llvm inside scratchbox you must use a newer qemu. See http://setanta.wordpress.com/2007/11/20/qemu-arm-eabi-no-scratchbox/ (in Portuguese, but the important things are in bash :) ) I don't know if it is the problem in this case, but it should be the first attempt. Lauro 2008/1/21, Rafael Espindola <espindola at google.com>: > On 21/01/2008, Arvind Ayyangar
2007 Nov 02
0
[LLVMdev] llvm-gcc bootsrtap on ARM
Rafael, Remember that the qemu <= 0.9.0 can misexecute code compiled by LLVM. I think you should test using qemu CVS. Lauro 2007/11/2, Rafael Espindola <espindola at google.com>: > Hello, > > I am trying to bootstrap on ARM linux EABI using a qemu chroot to > better test my changes on at least one more architecture. > > I am using the following configure line: >
2007 Mar 22
0
[LLVMdev] MSIL backend
Anton Korobeynikov wrote: > 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. > I'm
2007 Apr 02
1
[LLVMdev] Using LLVM as a crosscompiler
> > - Today LLVM supports ARM/EABI, but llvm-gcc don't. You must apply the > > patch: > > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070319/046070.html > > That doesn't apply anymore :( You must use the llvm-gcc4 from the svn. It has some bug fixes that are important to ARM EABI and the patch should apply cleanly. Lauro
2007 Apr 01
4
[LLVMdev] Using LLVM as a crosscompiler
Hi Koen, The process to build llvm-gcc as a crosscompiler is basically the same as build a normal gcc as crosscompiler. The differences: you need a LLVM installed (compiled for the host). You must configure llvm-gcc with --enable-llvm. Problems: - Today LLVM supports ARM/EABI, but llvm-gcc don't. You must apply the patch:
2007 Jan 17
3
[LLVMdev] LLVM ARM backend enhancements
I'm happy to announce that Apple is contributing some major extensions to the LLVM ARM backend. The improvements include support for ARM v4/v6, vfp support, soft float, pre/postinc support, load/ store multiple generation, constant pool entry motion (to support large functions), and support for the darwin/arm ABI. In addition to ARM support, the backend now includes code generation
2007 Feb 21
0
LLVM 2.0 Progress Report
Hi Everyone, I'm happy to say that LLVM has made many leaps and bounds since the last update in November. Because we are bumping the major version number with this release, we're letting the release go for twice as long as our planned release schedule (6 months instead of 3). We are currently half way through the LLVM 2.0 development cycle. So far, many important and invasive changes
2006 Dec 20
1
[LLVMdev] [patch] arm: external weak in constant pool
without tabs Lauro 2006/12/20, Bill Wendling <isanbard at gmail.com>: > > Hi Lauro, > > Just a stylistic remark; In your "llvm.patch" file, there are tabs in > these lines: > > + if (GV->hasExternalWeakLinkage()) { > + ExtWeakSymbols.insert(GV); > + } > > Others will need to review the patch for correctness, though. >
2006 Dec 20
0
[LLVMdev] [patch] arm: external weak in constant pool
Hi Lauro, Just a stylistic remark; In your "llvm.patch" file, there are tabs in these lines: + if (GV->hasExternalWeakLinkage()) { + ExtWeakSymbols.insert(GV); + } Others will need to review the patch for correctness, though. -bw On 12/20/06, Lauro Ramos Venancio <lauro.venancio at gmail.com> wrote: > Adds external weak symbols of constant pool to ExtWeakSymbols set.
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
2006 Nov 16
0
[LLVMdev] LLVM 1.9 Release Announcement [draft #1]
Hi All, Here's the first draft of the release announcement for LLVM 1.9 that I'm working on. I'm sure I've forgotten and overlooked something, if so, please let me know! ----- 8< ------ 8< ----- <notes> Note: LLVM now correctly builds itself and passes all regression tests on Darwin X86 and Darwin PPC. No one has tried other targets to my knowledge. We hit