Displaying 8 results from an estimated 8 matches for "lexpercent".
2007 Dec 15
2
[LLVMdev] fix warning with newer g++ compilers
...;
+
uint64_t Val = atoull(TokStart+1, CurPtr);
if ((unsigned)Val != Val)
GenerateError("Invalid value number (too large)!");
llvmAsmlval.UIntVal = unsigned(Val);
return GLOBALVAL_ID;
}
-
+
return '@';
}
@@ -305,11 +306,11 @@ int LLLexer::LexPercent() {
// Handle PctStringConstant: %\"[^\"]*\"
if (CurPtr[0] == '"') {
++CurPtr;
-
+
while (1) {
int CurChar = getNextChar();
-
- if (CurChar == EOF) {
+
+ if (CurChar == EOF) {
GenerateError("End of file in local v...
2013 Nov 27
0
[LLVMdev] Bug in Language Reference? %0 versus %1 as starting index.
...ix $ is the best syntax.
Maybe we could even get away with %42: as a BB label and that would be
maximally reminiscent. The way that numbered local variables are handled is
sort of ad-hoc (it is actually also handled in the Lexer; all the parser
sees is lltok::LocalVarID). By just changing LLLexer::LexPercent in
LLLexer.cpp to recognize a local label and emit a "LocalLabelID" token,
then adding an `else if` to the first `if` in LLParser::ParseBasicBlock,
you could probably get a working solution too. However, this introduces an
inconsistency in that now there's this pseudo-common syntax (%...
2013 Nov 27
2
[LLVMdev] Bug in Language Reference? %0 versus %1 as starting index.
...>
> Maybe we could even get away with %42: as a BB label and that would be
> maximally reminiscent. The way that numbered local variables are handled is
> sort of ad-hoc (it is actually also handled in the Lexer; all the parser
> sees is lltok::LocalVarID). By just changing LLLexer::LexPercent in
> LLLexer.cpp to recognize a local label and emit a "LocalLabelID" token,
> then adding an `else if` to the first `if` in LLParser::ParseBasicBlock,
> you could probably get a working solution too. However, this introduces an
> inconsistency in that now there's this pse...
2007 Dec 15
4
[LLVMdev] fix warning with newer g++ compilers
...xer::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: In member
function 'int llvm::LLLexer::LexPercent()':
/Volumes/mrs5/net/llvm/llvm/llvm/lib/AsmParser/LLLexer.cpp:338:
warning: suggest a space before ';' or explicit braces around empty
body in 'for' statement
/Volumes/mrs5/net/llvm/llvm/llvm/lib/AsmParser/LLLexer.cpp: In member
function 'int llvm::LLLexer::LexDigitOr...
2013 Nov 27
4
[LLVMdev] Bug in Language Reference? %0 versus %1 as starting index.
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 --------------
2013 Nov 27
0
[LLVMdev] Bug in Language Reference? %0 versus %1 as starting index.
...aybe we could even get away with %42: as a BB label and that would be
>> maximally reminiscent. The way that numbered local variables are handled is
>> sort of ad-hoc (it is actually also handled in the Lexer; all the parser
>> sees is lltok::LocalVarID). By just changing LLLexer::LexPercent in
>> LLLexer.cpp to recognize a local label and emit a "LocalLabelID" token,
>> then adding an `else if` to the first `if` in LLParser::ParseBasicBlock,
>> you could probably get a working solution too. However, this introduces an
>> inconsistency in that now ther...
2013 Nov 27
2
[LLVMdev] Bug in Language Reference? %0 versus %1 as starting index.
...d even get away with %42: as a BB label and that would be
>>> maximally reminiscent. The way that numbered local variables are handled is
>>> sort of ad-hoc (it is actually also handled in the Lexer; all the parser
>>> sees is lltok::LocalVarID). By just changing LLLexer::LexPercent in
>>> LLLexer.cpp to recognize a local label and emit a "LocalLabelID" token,
>>> then adding an `else if` to the first `if` in LLParser::ParseBasicBlock,
>>> you could probably get a working solution too. However, this introduces an
>>> inconsistency...
2013 Nov 27
0
[LLVMdev] Bug in Language Reference? %0 versus %1 as starting index.
...way with %42: as a BB label and that would be
>>>> maximally reminiscent. The way that numbered local variables are handled is
>>>> sort of ad-hoc (it is actually also handled in the Lexer; all the parser
>>>> sees is lltok::LocalVarID). By just changing LLLexer::LexPercent in
>>>> LLLexer.cpp to recognize a local label and emit a "LocalLabelID" token,
>>>> then adding an `else if` to the first `if` in LLParser::ParseBasicBlock,
>>>> you could probably get a working solution too. However, this introduces an
>>>>...