search for: lllexer

Ok, here is the patch again... I also included fixes for the bits that originally gave my mailer fits... Two votes for orange, so I went with orange... Doing diffs in .: --- ./lib/AsmParser/LLLexer.cpp.~1~ 2007-12-14 22:09:06.000000000 -0800 +++ ./lib/AsmParser/LLLexer.cpp 2007-12-15 13:02:47.000000000 -0800 @@ -54,7 +54,7 @@ static uint64_t HexIntToVal(const char * Result += C-'A'+10; else if (C >= 'a' && C <= 'f') Result += C-'a...

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/LLLexer.cpp:...

...with a new syntax that fits well and that won't break existing .ll files. The key places for making this round-trip are AssemblyWriter::printBasicBlock in lib/IR/AsmWriter.cpp and LLParser::ParseBasicBlock in lib/AsmParser/LLParser.cpp. The parsing side is likely to be entirely in lib/AsmParser/LLLexer.cpp where you need to find a way to get a new token "LocalLabelID" returned for the new syntax. To reiterate, the goal of such a change is solely to avoid people getting confused about the implicit numbering. It needs to be reminiscent/suggestive of the instruction numbering syntax to av...

...at fits well > and that won't break existing .ll files. The key places for making this > round-trip are AssemblyWriter::printBasicBlock in lib/IR/AsmWriter.cpp > and LLParser::ParseBasicBlock in lib/AsmParser/LLParser.cpp. The parsing > side is likely to be entirely in lib/AsmParser/LLLexer.cpp where you need > to find a way to get a new token "LocalLabelID" returned for the new syntax. > > To reiterate, the goal of such a change is solely to avoid people getting > confused about the implicit numbering. It needs to be > reminiscent/suggestive of the instructio...

Am 28.08.2011 20:02, schrieb geovanisouza92 at gmail.com: > Hi, Jo! > > I'm trying create a new programming language, and I want that it have > Unicode support (support for read and manipulate rightly the source-code and > string literals). > > But, in addition, my programming language supports "string interpolation" > string, and in these interpolations, tiny

The language reference states that local temporaries begin with index 0, but if I try that on my not-entirely-up-to-date v3.4 llc (it is like a week old), I get an error "instruction expected to be numbered '%1'". Also, quite a few examples in the LR uses %0 as a local identifier. Should I fix those or is it a problem in llc? -- Mikael -------------- next part --------------

...;> and that won't break existing .ll files. The key places for making this >> round-trip are AssemblyWriter::printBasicBlock in lib/IR/AsmWriter.cpp >> and LLParser::ParseBasicBlock in lib/AsmParser/LLParser.cpp. The parsing >> side is likely to be entirely in lib/AsmParser/LLLexer.cpp where you need >> to find a way to get a new token "LocalLabelID" returned for the new syntax. >> >> To reiterate, the goal of such a change is solely to avoid people getting >> confused about the implicit numbering. It needs to be >> reminiscent/suggesti...

...at won't break existing .ll files. The key places for making this >>> round-trip are AssemblyWriter::printBasicBlock in lib/IR/AsmWriter.cpp >>> and LLParser::ParseBasicBlock in lib/AsmParser/LLParser.cpp. The parsing >>> side is likely to be entirely in lib/AsmParser/LLLexer.cpp where you need >>> to find a way to get a new token "LocalLabelID" returned for the new syntax. >>> >>> To reiterate, the goal of such a change is solely to avoid people >>> getting confused about the implicit numbering. It needs to be >>>...

...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/lib/CodeGe...

...break existing .ll files. The key places for making this >>>> round-trip are AssemblyWriter::printBasicBlock in lib/IR/AsmWriter.cpp >>>> and LLParser::ParseBasicBlock in lib/AsmParser/LLParser.cpp. The parsing >>>> side is likely to be entirely in lib/AsmParser/LLLexer.cpp where you need >>>> to find a way to get a new token "LocalLabelID" returned for the new syntax. >>>> >>>> To reiterate, the goal of such a change is solely to avoid people >>>> getting confused about the implicit numbering. It needs to...

...urce-level function attribute is here: > http://reviews.llvm.org/D12922 > > http://reviews.llvm.org/D12923 > > Files: > docs/LangRef.rst > include/llvm/Bitcode/LLVMBitCodes.h > include/llvm/IR/Attributes.h > include/llvm/IR/Instructions.h > lib/AsmParser/LLLexer.cpp > lib/AsmParser/LLParser.cpp > lib/AsmParser/LLToken.h > lib/Bitcode/Reader/BitcodeReader.cpp > lib/Bitcode/Writer/BitcodeWriter.cpp > lib/CodeGen/SelectionDAG/SelectionDAGBuilder.cpp > lib/IR/Attributes.cpp > lib/IR/Verifier.cpp > lib/Transforms/...

Hello; I wanted to insert two new terminator instructions in LLVM IR. I modified the necessary files (as mentioned in the tutorial in LLVM site and some more to meet the new structure of LLVM, (e.g no Lexer.l now, we have LLLexer.cpp. Again in the tutorial, files like LLVMBitCodes.h, include/llvm-c/core.h that need to be modified are not mentioned) But I am getting the error while building LLVM. The SelectionDagBuilder.cpp file is giving the error. *In file included from /home/arnie/llvm-svn/llvm/lib/CodeGen/SelectionDAG...

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)': <llvm-root>/src/llvm/lib/AsmPars...

...port in LLVM. For example the patches do not parse the stepvector. > So I had to get inspired from the lib/AsmParser and lib/IR folders from https://github.com/ARM-software/LLVM-SVE (the ARM SVE LLVM compiler) and changed the following files in my LLVM 8.0 build: > llvm/lib/AsmParser/LLLexer.cpp > llvm/lib/AsmParser/LLParser.cpp > llvm/lib/AsmParser/LLParser.h > llvm/lib/AsmParser/LLToken.h > llvm/lib/IR/Instructions.cpp > llvm/include/llvm/IR/Constants.h > llvm/include/llvm/IR/Value.def > llvm/lib/IR/Constants.cpp > &gt...

...directly or indirectly down any possible call path. > > Repository: > rL LLVM > http://reviews.llvm.org/D14227 > > Files: > docs/LangRef.rst > include/llvm/Bitcode/LLVMBitCodes.h > include/llvm/IR/Attributes.h > include/llvm/IR/Function.h > lib/AsmParser/LLLexer.cpp > lib/AsmParser/LLParser.cpp > lib/AsmParser/LLToken.h > lib/Bitcode/Reader/BitcodeReader.cpp > lib/Bitcode/Writer/BitcodeWriter.cpp > lib/IR/Attributes.cpp > lib/IR/Verifier.cpp > test/Bindings/llvm-c/invalid-bitcode.test > test/Bitcode/attributes.ll &gt...

...kslash token >> >> Similarly to item 7 the backslash token doesn't seem to serve a purpose >> (with regards to release version 3.5.0 of the LLVM source code). Is it used >> somewhere? >> >> * Item 8 - quoted labels >> >> A comment in lib/AsmParser/LLLexer.cpp (once again, release version 3.5.0 >> of the LLVM source code) describes quoted labels using the following regexp >> (e.g. at least one character between the double quotes): >> >>> /// QuoteLabel "[^"]+": >> >> In contrast the refer...

...t; >>> To keep up with the spirit of the original topic here are a few more >>> items >>> :) >>> >>> * Item 11 - hexadecimal integer constants >>> >>> The lexer handles hexadecimal integer constants, e.g. from >>> lib/AsmParser/LLLexer.cpp >>> >>> /// HexIntConstant [us]0x[0-9A-Fa-f]+ >>>> >>> >>> This representation of integer constants is not mentioned in the language >>> specification as far as I can tell. >>> >>> >> I assume you are talking...

...VM > >> > >> http://reviews.llvm.org/D14227 > >> > >> Files: > >> docs/LangRef.rst > >> include/llvm/Bitcode/LLVMBitCodes.h > >> include/llvm/IR/Attributes.h > >> include/llvm/IR/Function.h > >> lib/AsmParser/LLLexer.cpp > >> lib/AsmParser/LLParser.cpp > >> lib/AsmParser/LLToken.h > >> lib/Bitcode/Reader/BitcodeReader.cpp > >> lib/Bitcode/Writer/BitcodeWriter.cpp > >> lib/IR/Attributes.cpp > >> lib/IR/Verifier.cpp > >> test/Bindings/ll...

The simplest way to run a clang test case that I know of is to clone both llvm and clang repos, run all the tests, then run an individual test. IIRC like so: git clone llvm ...... cd llvm/tools git clone clang ..... cd ../../ mkdir build cd build cmake ../llvm ninja check-clang ./bin/llvm-lit -v ./tools/clang/test/Sema/asm.c On Sun, May 6, 2018 at 7:10 AM, Sedat Dilek via llvm-dev <

I had a phone conversation yesterday with Graham, Francesco, and Kristof. There is one more reason to go with the native type change: ARM has already written the code with the SV types, and they have patches ready to be reviewed and integrated in LLVM. As I don't want to stand in the way of getting SVE in LLVM as soon as possible, I will also support the integration of the existing patches