Displaying 4 results from an estimated 4 matches for "r269096".
2016 May 26
2
Potential ambiguity in the grammar of LLVM IR assembly
...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:
To be fair, I believe it has been the case only for 2 weeks now (implemented in r269096).
--
Mehdi
>
> @<GlobalVarName> = [Linkage] [Visibility] [DLLStorageClass]
> [ThreadLocal] ...
>
> Cheers.
>
> Tim.
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/...
2016 May 26
0
Potential ambiguity in the grammar of LLVM IR assembly
Hello Mehdi,
Thank you for bringing this to our awareness. I've been looking into the
3.8 release of LLVM. Would you happen to know if r269096 was part of
this realese?
lli running on my system is capable of handling unnamed global
variables, so I'd imagine so.
u at x1 ~> lli -version
LLVM (http://llvm.org/):
LLVM version 3.8.0
Optimized build.
Built May 7 2016 (15:37:50).
Default target: x86_64-unknown-linux-gnu...
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.
2016 May 25
4
Potential ambiguity in the grammar of LLVM IR assembly
Hello everyone,
While developing a parser for LLVM IR, I seem to have stumbled upon a
potential ambiguity in the LLVM IR assembly language grammar. Most
likely there is something which I may have overlooked, so wanted to
reach out to a more experienced crowed for some feedback.
How would the following set of tokens be interpreted [1]?
declare
void
@foo()
unnamed_addr
global
i32
42
As far as