search for: mcasmlexer

...be overridden (probably copying most of the existing logic for the rest of the parsing anyway). I would like to find a more easy way to specify what to return as an identifier or separate logic allowing for more flexibility. I developed a tentative patch that adds this flexibility to the current MCAsmLexer infrastructure. I would like to gather opinions on this approach or ideas on other possible approaches to achieve something similar and find out if somebody else finds this kind of concept useful or not. Thanks, Marcello -------------- next part -------------- An HTML attachment was scrubbed... UR...

...n Zentrum fuer Informationsdienste und Hochleistungsrechnen Abteilung Verteiltes und Datenintensives Rechnen Zellescher Weg 12, 01069 Dresden Willersbau, Zimmer A105 Telefonnr.: +49 351 463-32442 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: MCAsmLexer.patch URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090729/bfd54e61/attachment.ksh> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Constants.patch URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090729/bfd5...

Please commit... Best Olaf Krzikalla -- Olaf Krzikalla Technische Universitaet Dresden Zentrum fuer Informationsdienste und Hochleistungsrechnen Abteilung Verteiltes und Datenintensives Rechnen Zellescher Weg 12, 01069 Dresden Willersbau, Zimmer A105 Telefonnr.: +49 351 463-32442 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: twine.patch

Hi ES, From what I understand instruction parsing is divided into two parts: - Parsing an operand list (XXXAsmParser::ParseInstruction) - Turning the operand list into an actual instruction (XXXAsmParser::MatchAndEmitInstruction) The second part does the validation (e.g. how many operands, what kind, etc) while the first part only does the parsing. That's why I think in the first part

...rectiveLoc) { diff --git a/lib/MC/MCParser/CMakeLists.txt b/lib/MC/MCParser/CMakeLists.txt index a5c0818..059f0fe 100644 --- a/lib/MC/MCParser/CMakeLists.txt +++ b/lib/MC/MCParser/CMakeLists.txt @@ -1,7 +1,7 @@ add_llvm_library(LLVMMCParser AsmLexer.cpp AsmParser.cpp + MachOAsmParser.cpp MCAsmLexer.cpp MCAsmParser.cpp - TargetAsmParser.cpp ) diff --git a/lib/MC/MCParser/MachOAsmParser.cpp b/lib/MC/MCParser/MachOAsmParser.cpp new file mode 100644 index 0000000..9c0802d --- /dev/null +++ b/lib/MC/MCParser/MachOAsmParser.cpp @@ -0,0 +1,630 @@ +//===- MachOAsmParser.cpp - Parser for Mach-O...

...m-2.8/include/llvm/MC/MCObjectWriter.h -- Installing: /usr/local/llvm-2.8/include/llvm/MC/MCParser -- Installing: /usr/local/llvm-2.8/include/llvm/MC/MCParser/AsmCond.h -- Installing: /usr/local/llvm-2.8/include/llvm/MC/MCParser/AsmLexer.h -- Installing: /usr/local/llvm-2.8/include/llvm/MC/MCParser/MCAsmLexer.h -- Installing: /usr/local/llvm-2.8/include/llvm/MC/MCParser/MCAsmParser.h -- Installing: /usr/local/llvm-2.8/include/llvm/MC/MCParser/MCAsmParserExtension.h -- Installing: /usr/local/llvm-2.8/include/llvm/MC/MCParser/MCParsedAsmOperand.h -- Installing: /usr/local/llvm-2.8/include/llvm/MC/MCSectio...

On Thu, Sep 30, 2010 at 3:08 PM, Samuel Williams <space.ship.traveller at gmail.com> wrote: > Hi, > > I might just be doing something stupid, but when I do > > $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. > $ sudo make install > > I don't get the expected headers in >        /usr/local/llvm-2.8/include/llvm > > It is

Hi, I might just be doing something stupid, but when I do $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. $ sudo make install I don't get the expected headers in /usr/local/llvm-2.8/include/llvm It is simply an empty directory. What am I doing wrong? This is on Mac OS X, CMake 2.8+ Kind regards, Samuel

...3]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/lib/MC/MCDisassembler' llvm[3]: Compiling ELFAsmParser.cpp for Release+Asserts build llvm[2]: Compiling ArchiveWriter.cpp for Release+Asserts build llvm[2]: Compiling LatencyPriorityQueue.cpp for Release+Asserts build llvm[3]: Compiling MCAsmLexer.cpp for Release+Asserts build make[2]: Entering directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/lib/Option' llvm[2]: Compiling Arg.cpp for Release+Asserts build llvm[2]: Compiling Binary.cpp for Release+Asserts build llvm[3]: Compiling MCAsmParser.cpp for Release+Asserts build llvm[2]: Compiling...