Displaying 20 results from an estimated 800 matches similar to: "[LLVMdev] one remaining CellSPU backend bug..."
2007 May 26
0
[LLVMdev] Problems compiling llvm-gcc4 frontend on x86_64
Hi Warren,
You have the -m32 flag set, but it's still giving you this:
> Warning: Generation of 64-bit code for a 32-bit processor requested.
> Warning: 64-bit processors all have at least SSE2.
But are you sure you want to compile the LLVM-GCC source? You should
use the binaries unless absolutely necessary.
-bw
On May 24, 2007, at 10:34 PM, Warren Armstrong wrote:
> Hi all,
2007 May 26
1
[LLVMdev] Problems compiling llvm-gcc4 frontend on x86_64
Hi Warren,
you can try to configure with the following
export CFLAGS="-m64"
export LDFLAGS="-L/usr/lib64"
LLVM:
../src/configure --prefix=`pwd`../install --enable-optimized --enable-jit
--enable-targets=host-only
make
LLVM-GCC:
../llvm-gcc4-2.0.source/configure --prefix=`pwd`../install
--program-prefix=llvm- --enable-llvm=/home/warren/llvm/obj/
--enable-languages=c,c++
2007 May 25
3
[LLVMdev] Problems compiling llvm-gcc4 frontend on x86_64
Hi all,
I've run into problems compiling the llvm-gcc frontend on x86_64. Is this
not supported, or am I making an error somewhere?
The procedure I followed was:
1. Download LLVM 2.0 source as a tarball (from a few days ago, during
the testing phase).
2. Download the llvm-gcc4 source today, as a tarball.
3. Extract both.
4. Configure LLVM as: ../src/configure --prefix=`pwd`../install
2008 Jan 12
1
[LLVMdev] Labels
I'm attempting to modify a parser generator to emit LLVM code instead of C.
So far the experience has been trivial, but I am now running into an error
regarding labels that I can't seem to solve.
Situation 1: A label is used immediately after a void function call (l6 in
this case):
<snip>
%tmp26 = load i32* @yybegin, align 4
%tmp27 = load i32* @yyend, align 4
call void
2008 May 07
1
[BioC] RCurl loading problem with 64 bit linux distribution
Martin,
Well, thanks for jumping in! We need all the help we can get ;)
I changed the execute bit as you suggested and recompiled, no luck, still
the same error message.
Below is the output you wanted me to look at, its a bit beyond me so I
include both a brief grep summary and then the whole enchilada. I do note
that my output is different from yours, but I'm not sure how to interpret.
I
2008 May 07
1
[BioC] RCurl loading problem with 64 bit linux distribution
Martin,
Well, thanks for jumping in! We need all the help we can get ;)
I changed the execute bit as you suggested and recompiled, no luck, still
the same error message.
Below is the output you wanted me to look at, its a bit beyond me so I
include both a brief grep summary and then the whole enchilada. I do note
that my output is different from yours, but I'm not sure how to interpret.
I
2008 Apr 21
3
[LLVMdev] Whole-function isel
I thought I'd share a little bit of progress I made this weekend.
I've gotten the first interesting test-case (a simple switch) through
hyperblock-based DAGISel, and there's a pretty picture too! Each part
of the switch is emitted directly into the DAG, rather than being
deferred.
This is the function:
define i32 @foo(i32 %x, i32 %z) nounwind {
entry:
switch i32 %x,
2016 May 17
2
How to debug if LTO generate wrong code?
> On May 17, 2016, at 1:33 AM, Shi, Steven via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Hello,
> Let me ask a LTO simple question again. For the llvm LTO example in the link:http://llvm.org/docs/LinkTimeOptimization.html <http://llvm.org/docs/LinkTimeOptimization.html>, I use below build commands to generate three different optimization level binary: -O0, -O1, -O2.
2006 Oct 24
1
[LLVMdev] InsertBranch called unconditionally?
According to the docs, InsertBranch should only be called if
AnalyzeBranch returns success. But in targets (like ARM or Sparc) that
don't implement them, the following test fails:
-----------------------------------
void %__gcov_init() {
entry:
switch uint 0, label %cond_true.i [
uint 0, label %UnifiedReturnBlock
uint 875573313, label
2008 Apr 22
0
[LLVMdev] Whole-function isel
Very nice! Why did you decide on hyperblock instead of SEME region and
how are you forming the blocks?
Evan
On Apr 20, 2008, at 9:59 PM, Christopher Lamb wrote:
> I thought I'd share a little bit of progress I made this weekend.
> I've gotten the first interesting test-case (a simple switch)
> through hyperblock-based DAGISel, and there's a pretty picture too!
>
2009 Jan 07
4
[LLVMdev] Possible bug in the ARM backend?
Hi,
I'm working on the iterated register coalescing graph coloring
allocator and try to test it with all backends available currently in
LLVM.
Initial tests with most of the backends are successful.
It turned out that my allocator triggers a specific assertion in the
RegScavenger and only for the ARM target. It looks like the LR
register is used for frame pointer related things,
but it is
2016 Feb 03
2
lld dynamic relocation creation issue
Hi all,
Working on lld aarch64 support I came across an issue where I am not sure which
would be best design approach to solve.
The aarch64 R_AARCH64_ABS64 relocation for PIC/PIE build requires a dynamic
relocation (R_AARCH64_RELATIVE) with the value set as the addend of the
relocation. For instance, when linking the crtbeginS.o which contains:
Relocation section '.rela.init_array' at
2008 Jul 24
2
[LLVMdev] Indirect Branch Representation
So, that means that &&(Label) operator, which is defined in C++, is also not
supported currently in LLVM. I thought I could obtain address of basic block
indirectly through this small hack but it does not seem to work.
Actually, I tried to make folloing dummy C++ code which uses this operator:
*int main(int argc,char** argv)
{
int x;
int y;
L1:
2008 Jul 24
0
[LLVMdev] Indirect Branch Representation
On Jul 23, 2008, at 8:47 PM, kapil anand wrote:
>
> Specifically, I need a way to represent indirect branch instruction
> (in binary) as an equivalent LLVM instruction. With switch
> instruction , I would have to list all the possible targets and then
> initialize the corresponding instruction. I was just thinking
> whether it might be possible to have some kind of
2008 Apr 27
1
[LLVMdev] Can't invoke an intrinsic?
In line 1157 of Verifier.cpp, there is this code:
Assert1(!F->isIntrinsic() || (i == 0 && isa<CallInst>(I)),
"Cannot take the address of an intrinsic!", &I);
This check appears to have a problem with this line:
invoke void @llvm.memcpy.i32( i8* %._items.i.i, i8*
%._items2.i.i, i32 ptrtoint (i32* getelementptr ([0 x i32]* null, i32 0,
2010 Dec 14
3
[LLVMdev] __used__ attributes in llvm-gcc's crtstuff.c
Hello,
I'm wondering why only some global static variables are marked with
__used__ attributes in llvm-gcc/gcc/crtstuff.c.
GCC compiles crtstuff.c with -fno-toplevel-reorder option, which ensures
that
unused static globals are not removed during optimization. However, since
LLVM does not support that option, I presume __used__ attribute is used
instead.
For example, __CTOR_LIST__[1]
2009 Jan 13
0
[LLVMdev] Possible bug in the ARM backend?
On Jan 7, 2009, at 2:48 AM, Roman Levenstein wrote:
> bb368: 0x8fdad00, LLVM BB @0x8fc2c98, ID#1:
> Predecessors according to CFG: 0x8fdac90 (#0)
> %R0<def> = MOVi 0, 14, %reg0, %reg0
> *** STR %LR<kill>, %R0<kill>, %reg0, 0, 14, %reg0, Mem:ST(4,4)
> [0x8fc2d68 + 0]
> %LR<def> = LDR <fi#0>, %reg0, 0, 14, %reg0
>
2009 Jan 13
2
[LLVMdev] Possible bug in the ARM backend?
2009/1/13 Evan Cheng <echeng at apple.com>:
>
> On Jan 7, 2009, at 2:48 AM, Roman Levenstein wrote:
>
>> bb368: 0x8fdad00, LLVM BB @0x8fc2c98, ID#1:
>> Predecessors according to CFG: 0x8fdac90 (#0)
>> %R0<def> = MOVi 0, 14, %reg0, %reg0
>> *** STR %LR<kill>, %R0<kill>, %reg0, 0, 14, %reg0, Mem:ST(4,4)
>> [0x8fc2d68 + 0]
2013 Oct 15
0
[LLVMdev] [llvm-commits] r192750 - Enable MI Sched for x86.
I should mention a couple of useful self-explanatory LLVM flags for triage:
-enable-misched=false
-verify-misched
-Andy
On Oct 15, 2013, at 4:43 PM, Eric Christopher <echristo at gmail.com> wrote:
> Grats on the work, a long time coming!
>
> Beware the incoming register allocation bugs ;)
>
> -eric
>
> On Tue, Oct 15, 2013 at 4:33 PM, Andrew Trick <atrick at
2008 Jul 24
5
[LLVMdev] Indirect Branch Representation
Specifically, I need a way to represent indirect branch instruction (in
binary) as an equivalent LLVM instruction. With switch instruction , I would
have to list all the possible targets and then initialize the corresponding
instruction. I was just thinking whether it might be possible to have some
kind of indirect branch where label is a "variable" and not an explicit
label present in