Displaying 6 results from an estimated 6 matches for "parsebasicblock".
2013 Nov 27
0
[LLVMdev] Bug in Language Reference? %0 versus %1 as starting index.
...others that this change
doesn't break previous .ll files.
It's just about thinking and coming up 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 i...
2013 Nov 27
2
[LLVMdev] Bug in Language Reference? %0 versus %1 as starting index.
...doesn't break previous .ll files.
>
> It's just about thinking and coming up 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
&...
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.
...evious .ll files.
>>
>> It's just about thinking and coming up 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...
2013 Nov 27
2
[LLVMdev] Bug in Language Reference? %0 versus %1 as starting index.
...t;>>
>>> It's just about thinking and coming up 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...
2013 Nov 27
0
[LLVMdev] Bug in Language Reference? %0 versus %1 as starting index.
...gt;>> It's just about thinking and coming up 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 s...