search for: dllstorageclass

...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.

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

Hi, I am absolutely new to LLVM. Currently reading through documentation and the C-API (which i want to use). As i am working on Windows, i was curios on how to specify an import which links to a function exported by a dll. The DLLStorageClass seems to be the wy to go, this seems clear. But after declaring a function for import, how do i specify the DLL the function is included in?

...lvm-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] ... That was changed quite recently: http://reviews.llvm.org/rL269096#c4361726 I guess that means that the grammar is not ambiguous here anymore (if it was before). -Manuel > Cheers. > > Tim. > _______________________________________________ > LLVM Develope...

...he LLVM IR parser reference implementation. The following extract from "lib/AsmParser/LLParser.cpp" illustrates that unnamed globals are allowed [2]. > /// ParseUnnamedGlobal: > /// OptionalVisibility (ALIAS | IFUNC) ... > /// OptionalLinkage OptionalVisibility OptionalDLLStorageClass > /// ... -> global variable > /// GlobalID '=' OptionalVisibility (ALIAS | IFUNC) ... > /// GlobalID '=' OptionalLinkage OptionalVisibility OptionalDLLStorageClass > ///...

On Tue, Apr 4, 2017 at 12:36 PM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > On 2017-Apr-04, at 12:12, Peter Collingbourne <peter at pcc.me.uk> wrote: > > On Mon, Apr 3, 2017 at 8:13 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> >> On Apr 3, 2017, at 7:08 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: >>

Hi, I don't find the formal definition of "declare", although it is used in ~300 hundred of places. Do I miss something? If it is not formally defined, should it be defined? Thanks. https://llvm.org/docs/LangRef.html -- Regards, Peng

...t; 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/cgi-bin/mailman/listinfo/llvm-dev