Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] 'make check' failed with: ... PHI node entries do not match predecessors! ..."
2005 Jun 20
0
[LLVMdev] 'make check' failed with: ... PHI node entries do not match predecessors! ...
Hi Henrik,
You don't have the latest C/C++ Front End Source code. Please update
from CVS to get the fix for the 2005-06-15-ExpandGotoInternalProblem.c
test. Note the date of the test (5 days ago).
Reid.
On Mon, 2005-06-20 at 18:42 +0200, Henrik Bach wrote:
> Hi,
>
> Now, I've build the tools and the cfe. However, 'make check' gave me the
> attached results.
2005 Jun 20
1
[LLVMdev] 'make check' failed with: ... PHI node entries donot match predece
Hi Reid,
Now, I've removed the file and updated the source tree with this command:
cvs -z3 -d :pserver:anon at llvm-cvs.cs.uiuc.edu:/var/cvs/llvm update -PdR llvm
However, the file still exits.
Henrik.
>From: Reid Spencer
>Date: Mon, 20 Jun 2005 10:57:54 -0700
>
>Hi Henrik,
>
>You don't have the latest C/C++ Front End Source code. Please update
>from CVS to get
2005 Jul 29
1
[LLVMdev] help with pointer-to-array conversion
OK, thanks Chris, I've found that running
opt -loopsimplify -instcombine -indvars -stats
gives me the setup I need for this transformation, and a small patch
makes it happen in the simple case we discussed. However, I'm having
some trouble when things get a bit more complicated with 3 nesting levels:
int A[3000000], B[20000], C[100], Z;
int main()
{
int i, j, k, *a, *b,
2005 Jun 18
2
[LLVMdev] The configure script seems to strip some / from path
Hi LLVMers,
The root of my SRC_DIR is: /home/hb/projects/src/llvm-1/llvm/
and the root of my OBJ_DIR is: /home/hb/projects/build/FC1/llvm-1-1.
However, the configure script seems to have stripped some of the / from the
paths:
Makefile.common:63: /home/hb/projects/buildFC1llvm-1-1/Makefile.config: No
such file or directory
Makefile.common:69: /home/hb/projects/srcllvm-1/Makefile.rules: No such
2005 Jun 18
0
[LLVMdev] The configure script seems to strip some / from path
On Sat, 2005-06-18 at 10:32 +0200, Henrik Bach wrote:
> Hi LLVMers,
>
> The root of my SRC_DIR is: /home/hb/projects/src/llvm-1/llvm/
> and the root of my OBJ_DIR is: /home/hb/projects/build/FC1/llvm-1-1.
>
> However, the configure script seems to have stripped some of the / from the
> paths:
> Makefile.common:63: /home/hb/projects/buildFC1llvm-1-1/Makefile.config: No
2005 Feb 22
2
[LLVMdev] Area for improvement
Sorry, I thought I was running selection dag isel but I screwed up when
trying out the really big array. You're right, it does clean it up
except for the multiplication.
So LoopStrengthReduce is not ready for prime time and doesn't actually
get used?
I might consider whipping it into shape. Does it still have to handle
getelementptr in its full generality?
Chris Lattner wrote:
2005 Jun 13
0
[LLVMdev] problem compiling the cfrontend on Linux/PPC
Cyrille Mescam wrote:
> On Mon, Jun 13, 2005 at 11:02:10AM -0500, John Criswell wrote:
>
>>Cyrille Mescam wrote:
>>
[snip]
>
> In fact, i am using the CFE build procedures. I am on instructions 5.
>
> cyrille
>
Okay, I took a closer look at your output.
I was correct in that gccas is attempting to assemble a native PPC
assembly language file. However,
2005 Jun 13
2
[LLVMdev] problem compiling the cfrontend on Linux/PPC
On Mon, Jun 13, 2005 at 11:02:10AM -0500, John Criswell wrote:
> Cyrille Mescam wrote:
> >Hi,
> >
> >
> >When compiling the cfrontend for Linux/PPC architecture on a powermac
> >G5, i got
> >the following error :
>
> I hate to ask a silly question, but are you using "make bootstrap" to
> build the cfrontend? Your output looks like gccas
2004 Mar 31
2
[LLVMdev] A question about induction variables
Hello,
I've just downloaded the latest release of LLVM, and playing with the
following simple example:
int main()
{
int r(0);
for (int i = 0; i < 100; ++i)
r += i;
;
return r;
}
I compile it and then run:
analyze -indvars x.bc
which prints:
Printing analysis 'Induction Variable Analysis' for function 'main':
and nothing else. It is a
2006 Jun 15
2
[LLVMdev] problem with loopinfo
hi,
The loopinfo pass failed to recognize the Tripcount of a simple program constructed by me, can you help me to figure out why this happened? Thanks.
The C program and corresponding .ll files are shown below. I used llvm1.7 to develop my own pass, and want to use the loop information.
-Wei
Test.c:
#include "stdio.h"
#define N 40
void func1() {
int a[N];
int i,j;
for
2004 Mar 31
0
[LLVMdev] A question about induction variables
On Wed, 31 Mar 2004, Vladimir Prus wrote:
> I've just downloaded the latest release of LLVM, and playing with the
> following simple example:
>
> int main()
> {
> int r(0);
> for (int i = 0; i < 100; ++i)
> r += i;
> ;
> return r;
> }
When I compiled it, I got the following LLVM code:
int %main() {
entry:
call void %__main( )
2006 Jun 15
2
[LLVMdev] problem with loopinfo
I did run the indvars pass, but it seemed that it didn't work.
-Wei
----- Original Message -----
From: "Chris Lattner" <sabre at nondot.org>
To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu>
Sent: Thursday, June 15, 2006 3:35 PM
Subject: Re: [LLVMdev] problem with loopinfo
> On Thu, 15 Jun 2006, Wei Jiang wrote:
>> hi,
>> The
2006 Jul 09
2
[LLVMdev] Critical edges
Dear guys,
I am having problem to split edges correctly. Mostly because the new
basic blocks are creating infinite loops. Could someone help me fixing the
code below? It is creating assembly like this one below. Block LBB1_9 was
inserted to break the critical edge between blocks LBB1_3 and LBB1_8. But
it changes the semantics of the original program, because, before, LBB1_8
was falling
2005 Feb 22
0
[LLVMdev] Area for improvement
On Mon, 21 Feb 2005, Jeff Cohen wrote:
> I noticed that fourinarow is one of the programs in which LLVM is much slower
> than GCC, so I decided to take a look and see why that is so. The program
> has many loops that look like this:
>
> #define ROWS 6
> #define COLS 7
>
> void init_board(char b[COLS][ROWS+1])
> {
> int i,j;
>
> for
2006 Jun 15
0
[LLVMdev] problem with loopinfo
On Thu, 15 Jun 2006, Wei Jiang wrote:
> hi,
> The loopinfo pass failed to recognize the Tripcount of a simple program constructed by me, can you help me to figure out why this happened? Thanks.
> The C program and corresponding .ll files are shown below. I used llvm1.7 to develop my own pass, and want to use the loop information.
What passes are you running before your pass? trip
2003 Dec 22
1
[LLVMdev] How to explain?
hi,
I want to know what is exact meaning in the following code.
target endian--
%struct..TorRec--
%struct.TorRec--
implementation--
;<sbyte>[#uses=1/0]--
how to explain them in details?
Does anyone give me a guide?
thanks
yueqiang
--------------------------------------------------------------
target endian = little
target pointersize = 32
%struct..TorRec = type { int, void ()* }
2005 Feb 22
5
[LLVMdev] Area for improvement
I noticed that fourinarow is one of the programs in which LLVM is much
slower than GCC, so I decided to take a look and see why that is so.
The program has many loops that look like this:
#define ROWS 6
#define COLS 7
void init_board(char b[COLS][ROWS+1])
{
int i,j;
for (i=0;i<COLS;i++)
for (j=0;j<ROWS;j++)
b[i][j]='.';
2006 Jul 05
0
[LLVMdev] Critical edges
> If you don't want critical edges in the machine code CFG, you're going to
> have to write a machine code CFG critical edge splitting pass: LLVM
> doesn't currently have one.
>
> -Chris
Hey guys,
I've coded a pass to break the critical edges of the machine
control flow graph. The program works fine, but I am sure it is not
the right way of implementing it.
2006 Jun 15
0
[LLVMdev] problem with loopinfo
On Thu, 15 Jun 2006, Wei Jiang wrote:
> I did run the indvars pass, but it seemed that it didn't work.
Then you'll have to trace through and find out why it's failing...
-Chris
> ----- Original Message ----- From: "Chris Lattner" <sabre at nondot.org>
> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu>
> Sent: Thursday, June 15,
2006 Jul 04
2
[LLVMdev] Critical edges
On Tue, 4 Jul 2006, Fernando Magno Quintao Pereira wrote:
> However, it does not remove all the critical edges. I am getting a very
> weird dataflow graph (even without the Break Critical edges pass). The
> dataflow generated by MachineFunction::dump() for the program below is
> given here:
> http://compilers.cs.ucla.edu/fernando/projects/soc/images/loop_no_crit2.pdf
...
> The