similar to: [LLVMdev] AsmParser is not robust

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 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:

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 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:

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, 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-uninitialized -Wno-comment -std=c++11

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 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

After waiting through about 2 hours of hard drive spinning for Clang to link under my Xubuntu Lucid Lynx Linux setup on VirtualBox, ld finally just gave up trying to link it. I was using CMake's build scripts on version 2.7 release of LLVM and Clang. The version of ld is (GNU Binutils for Ubuntu) 2.20.1-system.20100303. Can anyone confirm this problem? If needed I'll cross-post this to

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

Hi Jim, I did look at the ARMAsmParser and it seems to me that it is using a switch/case construct to change the opcode and the operands, but this construct may become too large eventually. I was wondering if it is possible to use isAsmParser only flag to call dedicated methods, like dedicated parsers for AsmOperands. Regards Vladimir ________________________________ From: Jim Grosbach [grosbach

Hi all, I'm working on llvm assembler support for Mips and for a while I'm trying to solve a problem regarding complex macro instructions. As mips assembler supports macro instructions that can develop to more then one real instruction depending on the operand type(usually two or three) we can't use InstAlias to exploit tableGen generated code. Currently we expand these in

----- Original Message ---- > From: Óscar Fuentes <ofv at wanadoo.es> > To: Samuel Crow <samuraileumas at yahoo.com> > Cc: Óscar Fuentes <ofv at wanadoo.es>; LLVM Developers Mailing List ><llvmdev at cs.uiuc.edu> > Sent: Fri, January 14, 2011 4:39:57 PM > Subject: Re: Circular Deps from CMake build using makefile > > Samuel Crow <samuraileumas

Hi Vladimir, ARM does similar things for complex assembly pseudos. Have a look at the definition and use of AsmPseudoInst in the ARM backend. They’re not typically expanding to multiple “real” instructions, but that’s an implementation detail, not a constraint. -Jim On Oct 1, 2013, at 5:36 AM, Vladimir Medic <Vladimir.Medic at imgtec.com> wrote: > Hi all, > I'm working on llvm

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 MCSymbol can live

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

Hello Óscar, This time the autotools version of LLVM trunk build with Clang trunk compiled in Debug+Asserts mode without complaint with --enable-bindings=none. I suspect this makes something fishy looking with the CMake build. Do you need logfiles from configure? Thanks again, --Sam ----- Original Message ---- > From: Óscar Fuentes <ofv at wanadoo.es> > To: Samuel Crow

Samuel Crow <samuraileumas at yahoo.com> writes: > This time the autotools version of LLVM trunk build with Clang trunk compiled in > Debug+Asserts mode without complaint with --enable-bindings=none. I suspect > this makes something fishy looking with the CMake build. Do you need logfiles > from configure? I'm clueless about what's happening there. The cyclic

Hello Óscar, The single-threaded build failed the same place as the double threaded build failed which is the same place I just indicated in my previous post. The ../llvm/configure script version failed with OCaml building with about 600 assembler errors since I built it in AMD64 mode. (Oops.) Should I disable OCaml from the configure script and try again? Assembler error, input left in