Displaying 7 results from an estimated 7 matches for "upgradeparser".
2007 Oct 26
2
[LLVMdev] llvm-build for ARM
...table llvm-dis (without
symbols)
make[2]: Leaving directory `/home/amitsingh/llvm-research
/llvm-source/obj/tools/llvm-dis'
make[2]: Entering directory
`/home/amitsingh/llvm-research/llvm-source/obj/tools/llvm-upgrade'
llvm[2]: Compiling UpgradeLexer.cpp for Release build
llvm[2]: Compiling UpgradeParser.cpp for Release build
UpgradeParser.tab.c: In function 'int Upgradeparse()':
UpgradeParser.tab.c:3937: error: Missing definition
for SSA_NAME: D.81521_38019in statement:
D.81521_328 = PHI <D.81521_38019(191), D.81521_37934(205), D.81521_37909(230),
D.81521_37741(231)>;
PHI argument
D....
2007 Oct 26
0
[LLVMdev] llvm-build for ARM
...> make[2]: Leaving directory `/home/amitsingh/llvm-research
> /llvm-source/obj/tools/llvm-dis'
> make[2]: Entering directory `/home/amitsingh/llvm-research/llvm-
> source/obj/tools/llvm-upgrade'
> llvm[2]: Compiling UpgradeLexer.cpp for Release build
> llvm[2]: Compiling UpgradeParser.cpp for Release build
> UpgradeParser.tab.c: In function 'int Upgradeparse()':
> UpgradeParser.tab.c:3937: error: Missing definition
> for SSA_NAME: D.81521_38019in statement:
> D.81521_328 = PHI <D.81521_38019(191), D.81521_37934(205), D.
> 81521_37909(230), D.81521_3774...
2008 Apr 14
0
[LLVMdev] llvm-as parse error
...on between signed and
unsigned integer expressions
/usr/share/bison.simple:626: warning: comparison between signed and
unsigned integer expressions
llvm[2]: Flexing UpgradeLexer.l
/usr/local/src/llvm-2.2/tools/llvm-upgrade/UpgradeLexer.l:405:
warning, rule cannot be matched
llvm[2]: Bisoning UpgradeParser.y
/usr/local/src/llvm-2.2/tools/llvm-upgrade/UpgradeParser.y:
conflicts: 8 shift/reduce, 7 reduce/reduce
I'm going to install older versions (those "officially" supported) of
the tools and try again.
--
Arto Vuori
avuori at cs.helsinki.fi
2008 Apr 14
2
[LLVMdev] llvm-as parse error
Hi:
I have just started to use llvm and confronted with a problem:
when I want to transform something very simple for name.ll to name.bc with llvm-as name.ll, some errors occured:
error: parse error, expecting `GLOBAL' or `CONSTANT' while reading token: 'target'
btw, the name.ll file is as follows:
; ModuleID = 'tst.bc'
target datalayout =
2007 Dec 14
0
[LLVMdev] LLVM SVN r45024 build failure on Debian Etch with GCC 4.1.2
...ebug build
llvm[2]: Linking Debug executable llvm-dis
llvm[2]: ======= Finished Linking Debug Executable llvm-dis
make[2]: Leaving directory `~/llvm/tools/llvm-dis'
make[2]: Entering directory `~/llvm/tools/llvm-upgrade'
llvm[2]: Compiling UpgradeLexer.cpp for Debug build
llvm[2]: Compiling UpgradeParser.cpp for Debug build
collect2: ld terminated with signal 15 [Terminated]
make[2]: *** [~/llvm/Debug/bin/opt] Error 1
make[2]: Leaving directory `~/llvm/tools/opt'
make[1]: *** [opt/.makeall] Error 2
make[1]: *** Waiting for unfinished jobs....
I've tried with GCC 3.3 as well to no avail.
CC...
2007 Jul 04
1
[LLVMdev] API design (and Boost and tr1)
...dy exists in Support/type_traits.h
so there is precedent for this.
Now, something is not quite right with the code as the overload doesn't seem
to get removed when passed an AllocaInst *. I'm working on figuring out why.
I wrote a small testcase which passes. I'm working on reducing
UpgradeParser.cc to a minimal testcase that shows the problem. I'm wondering
if I've stumbled on a gcc bug.
Is this an acceptable solution to the problem? Is importing these Boost
components ok? tr1 includes all of the Boost type traits so another option
is to just use those and impose a requirement...
2007 Jul 03
4
[LLVMdev] API design
On Monday 02 July 2007 16:26, Chris Lattner wrote:
> On Sun, 1 Jul 2007, Nick Lewycky wrote:
> > I've been running LLVM with _GLIBCXX_DEBUG (extra checks) turned on to
> > see what would happen, and it's been a complete disaster.
Well, that's a bit harsh, isn't it? It's finding bugs, just like it's
supposed to. :)
I believe I've started to run into