search for: asmparser

...lvm-commits/Week-of-Mon-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/...

...39;t build LLVM CFE after this patchs > 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----------------------------...

...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: >&g...

...this patchs > > 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: &g...

Hello! I see the following build failure of the sources at the top of the trunk, on x86_64. make[2]: Entering directory `<llvm-root>/build/llvm/lib/AsmParser' llvm[2]: Compiling LLLexer.cpp for Release build llvm[2]: Compiling LLParser.cpp for Release build <llvm-root>/src/llvm/lib/AsmParser/LLParser.cpp: In member function 'bool llvm::LLParser::ParseGlobal(const std::string&, const char*, unsigned int, bool, unsigned int)': <ll...

These warnings started appearing recently when building LLVM: llvm[2]: Compiling LLParser.cpp for Release build /Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp: In member function ‘bool llvm::LLParser::ParseBr(llvm::Instruction*&, llvm::LLParser::PerFunctionState&)’: /Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp:3195: warning: ‘Op1’ may be used uninitialized in this function /Volumes/Data/Users/kremenek/llvm/lib/AsmPars...

Hello With the latest LLVM from Subversion (rev48737 from http://llvm.org/svn/llvm-project/llvm/trunk) I'm getting make[2]: Entering directory `/usr/src/Lang/llvm/_Obj/lib/AsmParser' llvm[2]: Flexing Lexer.l llvm[2]: Compiling Lexer.cpp for Debug build /usr/src/Lang/llvm/lib/AsmParser/Lexer.l: In function 'int llvmAsmlex()': /usr/src/Lang/llvm/lib/AsmParser/Lexer.l:278: error: 'PURE' was not declared in this scope /usr/src/Lang/llvm/lib/AsmParser/Lexer.l:2...

Hello, The recent renamings moved some IR-related files and directories to more logical places. Is there a plan to rename lib/AsmParser as well? This directory name is somewhat misleading, because the code in it parses IR. In fact, nothing mentions AsmParser in the code inside that dir, except the build files. The name creates a confusion with other AsmParser citizens of LLVM like lib/MC/MCParser/AsmParser.cpp (which is an actual a...

I'm trying to build a standalone assembler for Mips using AsmParser and I'm facing a problem with assembly directives. Mips assembler has following syntax for .set directive .set reorder or .set noreorder which allow/disallow assembler to change the order of instructions in the block that follows. As the implemented AsmParser requires .set directive to...

...a project that had tried to call a function without arguments in the code but the declaration wasn't declared with a void parameter list. It failed with an assertion that something was trying to ++ past the end of an ilist. I seem to remember Chris Lattner saying when he made the hand written AsmParser that it wasn't intended to be very robust but, searching the list, I can't find the post where he said it. That being said, is this worthy of a bug report? An error message from the AsmParser would be preferred over a seemingly unrelated assert. Cheers, --Sam Crow

Hi. For weeks now I have problems compiling llvm from svn, compilation ends with llvm[2]: Compiling Lexer.cpp for Release build /home/borist/builds/llvm/lib/AsmParser/Lexer.l: In function 'int llvmAsmlex()': /home/borist/builds/llvm/lib/AsmParser/Lexer.l:278: error: 'PURE' was not declared in this scope /home/borist/builds/llvm/lib/AsmParser/Lexer.l:279: error: 'CONST' was not declared in this scope Lexer.cpp: In function 'int yy_g...

...> function without arguments in the code but the declaration wasn't > declared with a void parameter list. It failed with an assertion > that something was trying to ++ past the end of an ilist. > > I seem to remember Chris Lattner saying when he made the hand > written AsmParser that it wasn't intended to be very robust but, > searching the list, I can't find the post where he said it. That > being said, is this worthy of a bug report? An error message from > the AsmParser would be preferred over a seemingly unrelated assert. Please file a bug, it...

Hi all, I am trying to compile with a minimal TestAsmParser class, but I get the following error. ---------------- [43/780] Linking CXX executable bin/llvm-mc FAILED: : && /usr/bin/c++ -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-maybe-u...

Hi All, I wrote a very crude and simple AsmParser for my backend. llvm-tablegen also generates asm-matcher .inc file without any error. I have included the .inc file in my class for AsmParser. However, while building llvm, in linking stage for LTO, i am getting error - undefined reference to functions - ComputeAvailableFeatures, MatchInstructionI...

Hi everybody. I found that there are some problems with symbol location in AsmParser. 1. We need to know where symbol was declared. 2. We need to know where symbol was defined first time. There are two ways: 1. Add helper table to the parser with additional symbol info. But it takes additional memory consumption. 2. Add user tag (void*) for MCSymbol object. As I understood MCSymbo...

Newer g++ compilers can emit: /Volumes/mrs5/net/llvm/llvm/llvm/lib/AsmParser/LLLexer.cpp: In member function 'int llvm::LLLexer::LexAt()': /Volumes/mrs5/net/llvm/llvm/llvm/lib/AsmParser/LLLexer.cpp:287: warning: suggest a space before ';' or explicit braces around empty body in 'for' statement /Volumes/mrs5/net/llvm/llvm/llvm/lib/AsmParser/LLLe...

...s that creates the symbols. And in each place we need insert add its location info. I also found that MCContext has several create symbols methods, but all these methods uses CreateSymbol private method. So I see two possible ways here: 1. To aggregate all GetOrCreate-like symbol methods inside the AsmParser. So all asm parser extension like a COFFAsmParser should use aggregated methods instead of MCContext ones. And inside the aggregated methods we can add symbol location info. 2. Add create-symbol event to the MCContext. So each time when symbol will created by the MCContext::CreateSymbol this event...

...simple" in the low asm > layer appropriately? What am I missing? > > Thanks. > > include/llvm/MC/MCStreamer.h | 2 +- > lib/CodeGen/AsmPrinter/DwarfCFIException.cpp | 2 +- > lib/MC/MCAsmStreamer.cpp | 6 ++++-- > lib/MC/MCParser/AsmParser.cpp | 8 ++++++-- > lib/MC/MCStreamer.cpp | 2 +- > test/MC/AsmParser/cfi-startproc-simple.s | 7 +++++++ > 6 files changed, 20 insertions(+), 7 deletions(-) > create mode 100644 test/MC/AsmParser/cfi-startproc-simple.s > > diff --git a/i...

Dear Developers, I compile a OpenCL kernel, FFT, in AMDAPP SDK v2.5 using clang 3.8 + libclc and assembling the code with lld (The LLVM linker). The assembly code contains the following assembly codes (and lots of other similar format assembly) that fails to be parsed by AMDGPUAsmParser. It seems to me that both are valid instructions after looking at the SI instruction spec. s_mov_b32 s0, 0xfe5163ab v_mad_f32 v9, 0.5, v5, -v8 To reproduce this, I write this two lines in a text file and run llvm-mc -arch=amdgcn -mcpu=kaveri input.s The first line has the following error messag...

...VM to not delete the target blocks of my instruction? 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/li...