Displaying 3 results from an estimated 3 matches for "mewspring".
Did you mean:
measuring
2016 May 25
4
Potential ambiguity in the grammar of LLVM IR assembly
...s are valid in
the grammar [2]
declare void @foo() unnamed_addr
global i32 42
and [3]
declare void @foo()
unnamed_addr global i32 42
Is the grammar ambiguous, or is there something that I've overlooked?
Hope to hear back from you.
With kind regards,
Robin Eklind
[1]: https://github.com/mewspring/poc/blob/master/ll/a.ll
[2]: https://github.com/mewspring/poc/blob/master/ll/a1.ll
[3]: https://github.com/mewspring/poc/blob/master/ll/a2.ll
2016 May 26
1
Potential ambiguity in the grammar of LLVM IR assembly
...eresting possibilities.
Given that global variables may be unnamed, does the unnamed_addr
introduce an ambiguity in the LLVM IR grammar?
Cheers
/u
[1]: http://llvm.org/docs/LangRef.html
[2]:
https://github.com/llvm-mirror/llvm/blob/master/lib/AsmParser/LLParser.cpp#L432
[3]: https://github.com/mewspring/poc/blob/master/ll/b.ll
On 05/26/2016 02:42 AM, Tim Northover wrote:
> On 25 May 2016 at 16:10, Robin Eklind via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> declare void @foo() unnamed_addr
>> global i32 42
>
> Doesn't a global have to be named? The syntax i...
2016 May 26
0
Potential ambiguity in the grammar of LLVM IR assembly
On 25 May 2016 at 16:10, Robin Eklind via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> declare void @foo() unnamed_addr
> global i32 42
Doesn't a global have to be named? The syntax in the IR reference
doesn't make it optional:
@<GlobalVarName> = [Linkage] [Visibility] [DLLStorageClass]
[ThreadLocal] ...
Cheers.
Tim.