search for: llvmasmparser

...n-20060109/030639.html http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060109/030654.html Build terminated with messages: --8X---------------------------------------------- llvm[2]: Compiling Lexer.cpp for Debug build In file included from /Users/sabre/llvm/lib/AsmParser/Lexer.l:31: llvmAsmParser.tab.h:274:1: warning: "ESINT64VAL" redefined /home/wanderer/pkg/build/llvm/src/llvm/lib/AsmParser/llvmAsmParser.h:130:1: warning: this is the location of the previous definition llvmAsmParser.tab.h:275:1: warning: "EUINT64VAL" redefined /home/wanderer/pkg/build/llvm/src/llvm/li...

...hs > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060109/030639.html > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060109/030654.html This is most likely because you have conflict markers in the generated files in the lib/AsmParser directory. Try removing llvmAsmParser.[cpp,h] and Lexer.cpp and rebuilding. This is one really significant annoyance of having these files checked into CVS. Reid do you have any idea how we can solve this? -Chris > Build terminated with messages: > > --8X---------------------------------------------- > llvm[2]: Compil...

...ommits/Week-of-Mon-20060109/030639.html >> >> http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060109/030654.html >> > > > This is most likely because you have conflict markers in the generated > files in the lib/AsmParser directory. Try removing > llvmAsmParser.[cpp,h] and Lexer.cpp and rebuilding. > > This is one really significant annoyance of having these files checked > into CVS. Reid do you have any idea how we can solve this? > > -Chris > >> Build terminated with messages: >> >> --8X-----------------------------...

....cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060109/030639.html > > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060109/030654.html > > This is most likely because you have conflict markers in the generated > files in the lib/AsmParser directory. Try removing llvmAsmParser.[cpp,h] > and Lexer.cpp and rebuilding. > > This is one really significant annoyance of having these files checked > into CVS. Reid do you have any idea how we can solve this? > > -Chris > > > Build terminated with messages: > > > > --8X-----------------...

...::LLParser::ParseGlobal(const std::string&, const char*, unsigned int, bool, unsigned int)': <llvm-root>/src/llvm/lib/AsmParser/LLParser.cpp:446: warning: 'IsConstant' may be used uninitialized in this function llvm[2]: Compiling Parser.cpp for Release build llvm[2]: Compiling llvmAsmParser.cpp for Release build <llvm-root>/src/llvm/lib/AsmParser/llvmAsmParser.y:15:29: error: ParserInternals.h: No such file or directory <llvm-root>/src/llvm/lib/AsmParser/llvmAsmParser.y:83: error: 'ValID' was not declared in this scope <llvm-root>/src/llvm/lib/AsmParser/llvmA...

On Tue, Nov 07, 2006 at 10:39:46PM -0800, Tanya M. Lattner wrote: > cvs -d <CVS Repository> co -r release_19 llvm I'm getting a build error: llvm[2]: Compiling llvmAsmParser.cpp for Release build /rest/llvm/llvm/lib/AsmParser/llvmAsmParser.y: In function `int llvmAsmparse()': /rest/llvm/llvm/lib/AsmParser/llvmAsmParser.y:2105: error: expected `;' before '}' token /rest/llvm/llvm/lib/AsmParser/llvmAsmParser.y:2106: error: expected `;' before '}&...

Folks, Is anyone else the failure below? On Mac OS X everything builds properly... Thanks for any help, snaroff -------------- next part -------------- A non-text attachment was scrubbed... Name: Picture 27.png Type: image/png Size: 18959 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20081217/e7d37fee/attachment.png>

Sounds like this has to do with Bill backing out r61019, r61030, and r61040. I think 61031 (which update llvmAsmParser.cpp.cvs, etc.) should be backed out as well. Can someone do that? Evan On Dec 17, 2008, at 7:20 AM, Jean-Daniel Dupas wrote: > Got it. > > On Mac OS, the build process update the llvmAsmParser.cpp.cvs file, > and then generate llvmAsmParser.cpp from the .cvs file. > But on Windo...

Got it. On Mac OS, the build process update the llvmAsmParser.cpp.cvs file, and then generate llvmAsmParser.cpp from the .cvs file. But on Window, it does not update the .cvs files (probably because bison is missing), and so, the llvmAsmParser.cpp is not in sync with the .y file. As the Mac OS build process update the cvs files, commiting them after...

...ction? Here's a list of files I've modified so far: M llvm-2.3/include/llvm/CodeGen/SelectionDAGNodes.h M llvm-2.3/include/llvm/Instruction.def M llvm-2.3/include/llvm/Instructions.h M llvm-2.3/include/llvm/Support/InstVisitor.h M llvm-2.3/lib/AsmParser/LLLexer.cpp M llvm-2.3/lib/AsmParser/llvmAsmParser.cpp.cvs M llvm-2.3/lib/AsmParser/llvmAsmParser.h.cvs M llvm-2.3/lib/AsmParser/llvmAsmParser.y M llvm-2.3/lib/AsmParser/llvmAsmParser.y.cvs M llvm-2.3/lib/Bitcode/Reader/BitcodeReader.cpp M llvm-2.3/lib/Bitcode/Writer/BitcodeWriter.cpp M llvm-2.3/lib/CodeGen/SelectionDAG/LegalizeDAG.cpp M llvm-2.3/l...

...dly, it fails to build different subprojects with release and debug builds. In debug mode, it does not create the Analysis.lib, but this does not fail in release. This in turn precludes a successful general build in the debug mode. Thirdly, in release mode, MSVC complains about the use of Debug in llvmAsmParser.y 1>c:\llvm\lib\AsmParser\llvmAsmParser.y(3124) : error C2065: 'Debug' : undeclared identifier e.g. below. // common code from the two 'RunVMAsmParser' functions static Module* RunParser(Module * M) { llvmAsmlineno = 1; // Reset the current line number... CurModule.Curr...

...an LLVM problem but it affects LLVM. The problem is that bison 1.875 inserts an __attribute__((unused)) into the yyparse function after a label. The #define this is wrapped in thinks its legal anytime after release 2.0.93. With GCC 3.3.2, it gives a compiler error that looks like: > Compiling llvmAsmParser.cpp > llvmAsmParser.tab.c: In function `int llvmAsmparse()': > llvmAsmParser.tab.c:4152: error: parse error before `goto' > gmake: *** [/home/llvm/llvm/lib/AsmParser/Debug/llvmAsmParser.lo] Error 1 Perhaps support for this went away sometime in the 3.x releases of GCC. In any even...

...you will need to have bison and/or flex installed where Visual Studio can find them. Otherwise, you do not need them and the pre-generated files that come with the source tree will be used." One of errors of mine is as follows: ------------------------------------------------------- ... 7>llvmAsmParser.cpp 7>c1xx : fatal error C1083: Cannot open source file: '.\llvmAsmParser.cpp': No such file or directory ... ------------------------------------------------------- where llvmAsmParser.cpp is related to Bison so I am compelled to feel to try installing flex/bison on my machine, anyway....

I created the 1.9 release branch last night. As a reminder, please do not check in any code changes to the release branch. Please send me email if you have changes that need to be merged into the release branch. To check out the release branch: cvs -d <CVS Repository> co -r release_19 llvm cvs -d <CVS Repository> co -r release_19 llvm-test cvs -d <CVS Repository> co -r

...you will need to have bison and/or flex installed where Visual Studio can find them. Otherwise, you do not need them and the pre-generated files that come with the source tree will be used." One of errors of mine is as follows: ------------------------------------------------------- ... 7>llvmAsmParser.cpp 7>c1xx : fatal error C1083: Cannot open source file: '.\llvmAsmParser.cpp': No such file or directory ... ------------------------------------------------------- where llvmAsmParser.cpp is related to Bison so I am compelled to feel to try installing flex/bison on my machine, anyway....

...iles I've modified so far: > M llvm-2.3/include/llvm/CodeGen/SelectionDAGNodes.h > M llvm-2.3/include/llvm/Instruction.def > M llvm-2.3/include/llvm/Instructions.h > M llvm-2.3/include/llvm/Support/InstVisitor.h > M llvm-2.3/lib/AsmParser/LLLexer.cpp > M llvm-2.3/lib/AsmParser/llvmAsmParser.cpp.cvs > M llvm-2.3/lib/AsmParser/llvmAsmParser.h.cvs > M llvm-2.3/lib/AsmParser/llvmAsmParser.y > M llvm-2.3/lib/AsmParser/llvmAsmParser.y.cvs > M llvm-2.3/lib/Bitcode/Reader/BitcodeReader.cpp > M llvm-2.3/lib/Bitcode/Writer/BitcodeWriter.cpp > M llvm-2.3/lib/CodeGen/SelectionDA...

...nalysis.lib, but this does not fail in release. This in > turn precludes a successful general build in the debug mode. Strange, this works for me (tm). What doesn't build there? A single file? The whole module? > Thirdly, in release mode, MSVC complains about the use of > Debug in llvmAsmParser.y > 1>c:\llvm\lib\AsmParser\llvmAsmParser.y(3124) : error C2065: > 'Debug' : > 1>undeclared identifier > e.g. below. > // common code from the two 'RunVMAsmParser' functions static > Module* RunParser(Module * M) { > > llvmAsmlineno = 1; //...

.../Function.cpp (+33) include/llvm/Support/ManagedStatic.h (+4) lib/Support/ManagedStatic.cpp (+20) include/llvm/Bitcode/LLVMBitCodes.h (+3 -1) lib/Bitcode/Reader/BitcodeReader.cpp (+14 -1) lib/Bitcode/Writer/BitcodeWriter.cpp (+23 -10) lib/VMCore/AsmWriter.cpp (+2) lib/AsmParser/llvmAsmParser.y (+13 -3) lib/AsmParser/LLLexer.cpp (+1) lib/Transforms/Utils/CloneModule.cpp (+2) include/llvm-c/Core.h (+2) lib/VMCore/Core.cpp (+13) bindings/ocaml/llvm/llvm.ml (+2) bindings/ocaml/llvm/llvm_ocaml.c (+23) bindings/ocaml/llvm/llvm.mli (+9) test/Bindings/Ocaml/vmcore.ml (+...

...flex installed where Visual Studio can find them. > Otherwise, you do not need them and the pre-generated files that come > with the source tree will be used." > > One of errors of mine is as follows: > ------------------------------------------------------- > ... > 7>llvmAsmParser.cpp > 7>c1xx : fatal error C1083: Cannot open source file: > '.\llvmAsmParser.cpp': No such file or directory > ... > ------------------------------------------------------- > where llvmAsmParser.cpp is related to Bison so I am compelled to feel > to > try installing...

...ning to add a new instruction to the LLVM IR (and later to MIPS backend) for TLS(Thread level speculation) support. For this I tried to follow the steps described in http://llvm.org/docs/ExtendingLLVM dot html#instruction. But I could not find any llvm/lib/AsmParser/Lexer.l and llvm/lib/AsmParser/llvmAsmParser.y file in both the svn repository and the source code downloaded from the website. Could you tell me what are the files that need to be modified to add a new token to parse my instruction from assembly text file (STEP 4) and add the grammar on how my instruction can be read and what it will constr...