search for: lltoken

...12922 > > 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/Scalar/TailRecursionElimination.cpp > test/Bindings/llvm-c/Inpu...

...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 > > However, things seems to be a bit more complicated - it seems I need to patch also files in the clang folder also (https:...

...itory: > 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 > test/Bitcode/compatibility.ll > test/Bitcode/invalid.ll &g...

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

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

...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/Scalar/TailRecursionE...

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

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

...ot; linkage may only be applied to global variables of pointer to array type. Similarly to item 4 this restriction isn't enforced by the parser. Would it make sense doing so, or is there any problem with such an approach? * Item 6 - hash token The hash token (#) is defined in lib/AsmParser/LLToken.h (release version 3.5.0 of the LLVM source code) but doesn't seem to be used anywhere else in the source tree. Is this token a historical artefact or does it serve a purpose? * Item 7 - backslash token Similarly to item 7 the backslash token doesn't seem to serve a purpose (with rega...

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

...git-llvm to add a –verbose option: `git apply --verbose -p2 -` returned 1 Checking patch include/llvm/IR/DebugInfoFlags.def... Checking patch include/llvm/IR/DebugInfoMetadata.h... Checking patch lib/AsmParser/LLLexer.cpp... Checking patch lib/AsmParser/LLParser.cpp... Checking patch lib/AsmParser/LLToken.h... Checking patch lib/Bitcode/Reader/MetadataLoader.cpp... Checking patch lib/Bitcode/Writer/BitcodeWriter.cpp... Checking patch lib/IR/AsmWriter.cpp... Checking patch lib/IR/DebugInfoMetadata.cpp... Checking patch test/Assembler/disubprogram.ll... Checking patch test/Assembler/invalid-disubprogr...

...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/Attribu...

...> >>> Similarly to item 4 this restriction isn't enforced by the parser. Would >>> it make sense doing so, or is there any problem with such an approach? >>> >>> * Item 6 - hash token >>> >>> The hash token (#) is defined in lib/AsmParser/LLToken.h (release version >>> 3.5.0 of the LLVM source code) but doesn't seem to be used anywhere else >>> in >>> the source tree. Is this token a historical artefact or does it serve a >>> purpose? >>> >>> >> Try deleting it. If the tests pa...

...> to array type. >> >> Similarly to item 4 this restriction isn't enforced by the parser. Would >> it make sense doing so, or is there any problem with such an approach? >> >> * Item 6 - hash token >> >> The hash token (#) is defined in lib/AsmParser/LLToken.h (release version >> 3.5.0 of the LLVM source code) but doesn't seem to be used anywhere else in >> the source tree. Is this token a historical artefact or does it serve a >> purpose? >> > > Try deleting it. If the tests pass send a patch. Same for item 7. > &g...

...git-llvm to add a –verbose option: `git apply --verbose -p2 -` returned 1 Checking patch include/llvm/IR/DebugInfoFlags.def... Checking patch include/llvm/IR/DebugInfoMetadata.h... Checking patch lib/AsmParser/LLLexer.cpp... Checking patch lib/AsmParser/LLParser.cpp... Checking patch lib/AsmParser/LLToken.h... Checking patch lib/Bitcode/Reader/MetadataLoader.cpp... Checking patch lib/Bitcode/Writer/BitcodeWriter.cpp... Checking patch lib/IR/AsmWriter.cpp... Checking patch lib/IR/DebugInfoMetadata.cpp... Checking patch test/Assembler/disubprogram.ll... Checking patch test/Assembler/invalid-disubprogr...

...git-llvm to add a –verbose option: `git apply --verbose -p2 -` returned 1 Checking patch include/llvm/IR/DebugInfoFlags.def... Checking patch include/llvm/IR/DebugInfoMetadata.h... Checking patch lib/AsmParser/LLLexer.cpp... Checking patch lib/AsmParser/LLParser.cpp... Checking patch lib/AsmParser/LLToken.h... Checking patch lib/Bitcode/Reader/MetadataLoader.cpp... Checking patch lib/Bitcode/Writer/BitcodeWriter.cpp... Checking patch lib/IR/AsmWriter.cpp... Checking patch lib/IR/DebugInfoMetadata.cpp... Checking patch test/Assembler/disubprogram.ll... Checking patch test/Assembler/invalid-disubprogr...

...il/llvmdev/2014-October/077715.html IMO, the files to focus on are: include/llvm/IR/DebugInfo.h include/llvm/IR/DebugLoc.h include/llvm/IR/Metadata.h include/llvm/IR/Value.h lib/AsmParser/LLLexer.cpp lib/AsmParser/LLParser.cpp lib/AsmParser/LLParser.h lib/AsmParser/LLToken.h lib/Bitcode/Reader/BitcodeReader.cpp lib/Bitcode/Writer/BitcodeWriter.cpp lib/Bitcode/Writer/ValueEnumerator.cpp lib/Bitcode/Writer/ValueEnumerator.h lib/IR/AsmWriter.cpp lib/IR/AsmWriter.h lib/IR/DebugInfo.cpp lib/IR/DebugLoc.cpp lib/IR/LLVMContextImpl.cpp...

...t;>>> it make sense doing so, or is there any problem with such an >>>>>>> approach? >>>>>>> >>>>>>> * Item 6 - hash token >>>>>>> >>>>>>> The hash token (#) is defined in lib/AsmParser/LLToken.h (release >>>>>>> version >>>>>>> 3.5.0 of the LLVM source code) but doesn't seem to be used anywhere >>>>>>> else >>>>>>> in >>>>>>> the source tree. Is this token a historical artefact or...

OK, I've managed to do it: I was trying to push it from a build/ directory, maybe that's why the git apply was failing. Pushing the commit from the root of the repo worked. Em qua, 28 de nov de 2018 às 16:40, Mikhail Ramalho < mikhail.ramalho at gmail.com> escreveu: > Hi, > > The patch only changes one file in clang. Here's the patch: >

...AttrBuilder &B) { case lltok::kw_ssp: case lltok::kw_sspreq: case lltok::kw_sspstrong: + case lltok::kw_safestack: case lltok::kw_uwtable: HaveError |= Error(Lex.getLoc(), "invalid use of function-only attribute"); break; diff --git a/lib/AsmParser/LLToken.h b/lib/AsmParser/LLToken.h index f9821f7..fbc0384 100644 --- a/lib/AsmParser/LLToken.h +++ b/lib/AsmParser/LLToken.h @@ -132,6 +132,7 @@ namespace lltok { kw_ssp, kw_sspreq, kw_sspstrong, + kw_safestack, kw_sret, kw_sanitize_thread, kw_sanitize_memory, diff --git a...