search for: venancio

Displaying 20 results from an estimated 48 matches for "venancio".

2006 Dec 20
1
[LLVMdev] [patch] arm: external weak in constant pool
..."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. > > > > > > Lauro > > > > _______________________________________________ > > LLVM Developers mailing list > > LLVMdev at cs.uiuc.edu...
2006 Dec 20
2
[LLVMdev] [patch] arm: external weak in constant pool
Adds external weak symbols of constant pool to ExtWeakSymbols set. Lauro -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20061220/1aaa0c7b/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm.patch Type: text/x-patch Size: 1021 bytes Desc: not available
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. > > > Lauro > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http:/...
2007 Feb 27
2
[LLVMdev] another problem with function arguments aligment
I think, we must move function arguments lowering from frontend to LLVM core. This lowering is generating machine dependent bytecode. See http://llvm.org/bugs/show_bug.cgi?id=1230 Lauro 2007/2/26, Chris Lattner <sabre at nondot.org>: > On Mon, 26 Feb 2007, Lauro Ramos Venancio wrote: > > The problem is: llvm-gcc generates the same bytecode for both functions: > > > > declare void @f(i32, i64) > > declare void @g(i32, i64) > > > > I can't differ an i64 argument from a struct argument. > > Oops. You can fix this by changing ll...
2007 Aug 13
6
[LLVMdev] LLVM performance test
Hi all, I did a performance test of two real applications (FFMPEG and GTK) on ARM. For more details see: http://laurovenancio.wordpress.com/2007/08/07/llvm-perf-tests/ Lauro
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 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:
2010 Nov 26
2
[LLVMdev] ARM Intruction Constraint DestReg!=SrcReg patch?
...t; The advise would be to assume that restriction still applies to ARMv4T or > ARMv5TE when developing portable code Thus, if I want to follow this advice, is there a way to force LLVM to not output instructions such as "mul r0, r0, r2"? As I believe was the effect of the Lauro Ramos Venancio's patch. kind regards, Maarten Faddegon
2007 Feb 26
0
[LLVMdev] another problem with function arguments aligment
On Mon, 26 Feb 2007, Lauro Ramos Venancio wrote: > The problem is: llvm-gcc generates the same bytecode for both functions: > > declare void @f(i32, i64) > declare void @g(i32, i64) > > I can't differ an i64 argument from a struct argument. Oops. You can fix this by changing llvm-gcc: gcc/llvm-abi.h Grep for instan...
2007 Apr 10
2
[LLVMdev] LLVM and TLS
Hi all, I'm trying to make a toolchain for arm-linux-gnueabi using the llvm-gcc. To do this, I made some changes in crosstool 0.42. Everything goes fine until llvm-gcc tries to compile the glibc. llvm-gcc can't compile glibc because it doesn't support TLS (Thread Local Storage). I know there is a bug report about TLS (PR941). Is there someone implementing TLS in LLVM and llvm-gcc?
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: >
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
2008 Jan 21
0
[LLVMdev] LLVM build freezes in scratchbox, ARM target
On Jan 21, 2008 7:47 PM, Lauro Ramos Venancio <lauro.venancio at gmail.com> wrote: > 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 have an installation of qemu...
2008 Feb 04
1
[LLVMdev] llc fails to generate code for arm
...is not supported in this configuration. The configure options were : /home/arvind/llvm/llvm-gcc4.2-2.1.source/configure --prefix=/opt/llvm/ --enable-threads --disable-nls --disable-shared --enable-languages=c --enable-sjlj-exceptions --program-prefix=llvm- On Jan 28, 2008 8:18 PM, Lauro Ramos Venancio <lauro.venancio at gmail.com> wrote: > HI Arvind, > > I think you are using an old llc version. VarArg support was > implemented a long time ago. > > Lauro > > 2008/1/28, Arvind Ayyangar <arvind.ayyangar at gmail.com>: > > > Hi all, > > I had...
2007 Jan 05
0
[LLVMdev] constant pool in large functions
...ded with a custom instrinfo that specify instruction length for each target instruction. 2. Probably some kind of constantpool pseudo instruction. The pass can then insert new constantpool instructions at the right locations to solve this problem. Evan On Jan 5, 2007, at 9:15 AM, Lauro Ramos Venancio wrote: > I'm facing a problem with constant pool in large functions. > > The LLVM prints constant pool at the beginning of functions. > > In large functions loads can be far from constant pool. GCC > resolves this situations by spreading constants throughtout > functio...
2007 Aug 14
0
[LLVMdev] LLVM performance test
Hi Lauro, On 14 Aug 2007, at 01:10, Lauro Ramos Venancio wrote: > Hi all, > > I did a performance test of two real applications (FFMPEG and GTK) on > ARM. For more details see: > http://laurovenancio.wordpress.com/2007/08/07/llvm-perf-tests/ Could you give me some more information about the applications you compiled and ran? Where can...
2007 Feb 09
0
[LLVMdev] problem with function arguments in ARM EABI
...e, 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 attribute. Chris, got a better idea? Evan On Feb 9, 2007, at 1:57 PM, Lauro Ramos Venancio wrote: >> >> 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 w...
2008 Jan 28
0
[LLVMdev] llc fails to generate code for arm
HI Arvind, I think you are using an old llc version. VarArg support was implemented a long time ago. Lauro 2008/1/28, Arvind Ayyangar <arvind.ayyangar at gmail.com>: > Hi all, > I had little success installing llvm inside scratchbox for an ARM > build so have been trying to generate assembly code for arm using the > llc utility. However, llc fails to generate code for
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 Jan 05
2
[LLVMdev] constant pool in large functions
I'm facing a problem with constant pool in large functions. The LLVM prints constant pool at the beginning of functions. In large functions loads can be far from constant pool. GCC resolves this situations by spreading constants throughtout functions. A C test and the code generated by LLVM and GCC are attached. As you can see in the following error the ldr is too far from constant: $