similar to: [LLVMdev] If you have build problems in tblgen or lib/AsmParser...

On Jan 31, 2012, at 1:26 PM, Carter, Jack wrote: > I'm trying to build a standalone assembler for Mips using AsmParser. > > Following the lead of X86, ARM and MBlaze I have run tblgen -gen-asm-matcher on Mips.td to produce tables and methods to aid the parser (MipsAsmParser.cpp) which is a stripped down ARM implementation. > > I am getting an assertion for what I believe are

Hi Jack, You're running into a fundamental problem with the current table generated asmmatcher. Specifically, wants to believe that assembly parsing is context insensitive, or at least close enough that operands can be parsed w/o knowing the context of the instruction. Its idea is to use the operand types to disambiguate which instruction should be selected. It sounds like MIPS 64vs.32 does

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

I'm trying to build a standalone assembler for Mips using AsmParser. Following the lead of X86, ARM and MBlaze I have run tblgen -gen-asm-matcher on Mips.td to produce tables and methods to aid the parser (MipsAsmParser.cpp) which is a stripped down ARM implementation. I am getting an assertion for what I believe are multiple register definitions with the same name. llvm-tblgen:

Hi, everyone. Does anyone faced with the MSVC Debug build issues of clang-tblgen and llvm-tblgen? I'm using Windows10 Pro. MSVC and GCC. Here is my cmake setup: cmake -GNinja ../llvm -DLLVM_ENABLE_PROJECTS=clang -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_BUILD_TYPE=Debug When building debug with GCC, cmd shows next: D:\llvm-project\buildn2\bin>clang-tblgen.exe --version LLVM

On Nov 13, 2009, at 10:16 AM, Samuel Crow wrote: > Hello all, > > My partner was just debugging 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

Hello all, My partner was just debugging 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

For VC++, I solved this by having bison/flex put the files into the obj directories. I also have it unconditionally regenerate the files if bison/flex is available, and copy them from src if they are not. Chris Lattner wrote: > On Wed, 11 Jan 2006, Vladimir A. Merzliakov wrote: > >> I can't build LLVM CFE after this patchs >>

No solutions come to mind. Conflicts are conflicts and must be resolved manually. This situation should only occur if you change the .l/.y file and then update the .h/.cpp files after someone else has changed the .l/.y file and regenerated the .h and .cpp. That doesn't seem like a high frequency scenario that we need to worry about. Not sure there's much we could do even if it was. Reid.

Hi all, when trying to build LLVM+Clang (r180247) on a BlueGene/Q, I get the following error message (multiple times): llvm[3]: Building PPC.td code emitter with tblgen llvm-tblgen: Unknown command line argument '-gen-emitter'. Try: '/homea/jjsc13/jjsc1301/.pool/.build/llvm_r180241/Release+Asserts/bin/llvm-tblgen -help' llvm-tblgen: Did you mean '-mc-emitter'? Has

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:

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 have the following syntax:

On Wed, 11 Jan 2006, Vladimir A. Merzliakov wrote: > I can'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

On the trunk version of LLVM I am getting the following build error on Snow Leopard (v10.6.2): llvm[3]: Building X86.td DAG instruction selector implementation with tblgen Assertion failed: (LHS->ID != RHS->ID), function operator(), file /Users/peckw/Projects/llvm/llvm-pristine/utils/TableGen/DAGISelEmitter.cpp, line 183. ... <cut - see full_stack_trace.txt> 0. Program arguments:

Hi all, I'm building clang on Ubuntu LTS 12.04 and it started blowing up since yesterday: $ make update svn update /home/csabaraduly/workspace/LLVM/llvm At revision 183495. At revision 183495. At revision 183495. At revision 183495. $ make all VERBOSE=1 for dir in lib/Support lib/TableGen utils lib/IR lib tools/llvm-config tools runtime docs unittests; do \ if ([ ! -f $dir/Makefile ] ||

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, MatchInstructionImpl, MatchRegisterName and

Now I see, that its to so trivial as I thought before. There are a lots of parser extensions 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

Hi, In another post I was trying to find out how to use libc++ instead of libstdc++ when compiling llvm/clang. I couldnt find the a way to tell cmake to do that. So I switched to using configure to compile llvm/clang. But now I find that the artifacts produced are different. Here are the issues I see: - configure doesnt seem to respect '--prefix' option, it just puts

On 01/24/2013 02:38 PM, Ulrich Weigand wrote: > > Hello, > > on PowerPC and a couple of other platforms, the GNU assembler allows using > a stand-alone '$' as part of an expression, and interprets it to refer to > the current PC just like '.'. (You can still use '$' as part of > identifiers otherwise.) For compatibility, we need to model the same

I can'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 Build terminated with messages: --8X---------------------------------------------- llvm[2]: Compiling Lexer.cpp for Debug build In file included from