[llvm-dev] Potential ambiguity in the grammar of LLVM IR assembly
Mehdi Amini via llvm-dev
llvm-dev at lists.llvm.org
Wed May 25 19:06:16 PDT 2016
> On May 25, 2016, at 7:02 PM, Robin Eklind <roek4411 at student.uu.se> wrote:
> 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 realize?
No it isn't in 3.8.
(I also mentioned in my email that it happened two weeks ago, which is obviously far after the 3.8 release).
> 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
> Host CPU: broadwell
> Cheers /u
> On 05/26/2016 03:55 AM, Mehdi Amini wrote:
>>> On May 25, 2016, at 5:42 PM, Tim Northover via llvm-dev <llvm-dev at lists.llvm.org> 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 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).
More information about the llvm-dev