search for: langref

...nd build great online docs there! Of course by its nature, MLIR doesn't lend itself to concrete semantic > descriptions, though I would expect the affine dialect (and others) to > have documentation on par with the LLVM IR. Just last week I had to scout through the affine dialect "LangRef <https://github.com/tensorflow/mlir/blob/master/g3doc/Dialects/Affine.md>" for something, and I also felt that it is due for a refresh! It seemed a bit more than just BNF though, do you have example of what you would like to see expanded there? And to be clear: the ambition should be th...

...y its nature, MLIR doesn't lend itself to concrete semantic > >> descriptions, though I would expect the affine dialect (and others) to > >> have documentation on par with the LLVM IR. > > > > > > Just last week I had to scout through the affine dialect "LangRef > > <https://github.com/tensorflow/mlir/blob/master/g3doc/Dialects/Affine.md > >" > > for something, and I also felt that it is due for a refresh! It seemed a > > bit more than just BNF though, do you have example of what you would like > > to see expanded ther...

...t; Sent: 27 de novembro de 2019 01:10 To: Nuno Lopes <nuno.lopes at ist.utl.pt>; LLVMdev <llvm-dev at lists.llvm.org> Cc: spatel at rotateright.com; Juneyoung Lee <juneyoung.lee at sf.snu.ac.kr>; zhengyang-liu at hotmail.com; John Regehr <regehr at cs.utah.edu> Subject: RE: LangRef semantics for shufflevector with undef mask is incorrect The shuffle mask of a shufflevector is special: it's required to be a constant in a specific form. From LangRef: "The shuffle mask operand is required to be a constant vector with either constant integer or undef values." So...

Hi Duncan, >>> and instcombine adds the explicit alignment according to >>>> the langref (pref alignment). >>> >>> Without an explicit alignment means the ABI alignment in the case of >>> loads/stores. >> >> Yes, that second step was clear. Assuming you meant the "preferential >> alignment", according to the langref. > > no,...

Hi, This is a follow up on a discussion around shufflevector with undef mask in https://reviews.llvm.org/D70641 and https://bugs.llvm.org/show_bug.cgi?id=43958. The current semantics of shufflevector in http://llvm.org/docs/LangRef.html#shufflevector-instruction states: "If the shuffle mask is undef, the result vector is undef. If any element of the mask operand is undef, that element of the result is undef." We found this semantics to be problematic. TL;DR: instructions can't detect if an operand is undef. L...

Hello, I believe llvm.rint description in LangRef is not quite complete. Llvm seems to map math.h:rint() call to llvm.rint intrinsic, and the LangRef says that the result of llvm.rint matches the result of libm rint() call. Next, LangRef states that llvm.rint "returns the operand rounded to the nearest integer." Shouldn't the spec...

...Metadata won't work. Metadata is defined to not affect code correctness and this obviously does. > > > Is it true for Module level Metadata and not only for instruction attached one? There are examples of module-level metadata that impact the correctness of the generated code in the LangRef today: http://llvm.org/docs/LangRef.html#module-flags-metadata <http://llvm.org/docs/LangRef.html#module-flags-metadata> http://llvm.org/docs/LangRef.html#objective-c-garbage-collection-module-flags-metadata <http://llvm.org/docs/LangRef.html#objective-c-garbage-collection-module-flags-me...

...k. Metadata is defined to not affect code correctness and this obviously does. >> >> >> Is it true for Module level Metadata and not only for instruction attached one? > > There are examples of module-level metadata that impact the correctness of the generated code in the LangRef today: > > http://llvm.org/docs/LangRef.html#module-flags-metadata <http://llvm.org/docs/LangRef.html#module-flags-metadata> > http://llvm.org/docs/LangRef.html#objective-c-garbage-collection-module-flags-metadata <http://llvm.org/docs/LangRef.html#objective-c-garbage-collection-...

...iced that it is possible to programmatically construct a cmpxchg instruction operating on floats (or actually any type since there is no assertion on pointer element type here https://github.com/llvm/llvm-project/blob/9c2e708f0dc547d386ea528450a33ef4bd2a750b/llvm/lib/IR/Instructions.cpp#L1501), but LangRef specifies that only integers and pointers are accepted ( https://llvm.org/docs/LangRef.html#cmpxchg-instruction). Does somebody rely on other types being accepted in cmpxchg or should we add an assertion for the element type to match the LangRef? -- Alex -------------- next part -------------- An...

...a is defined to not affect code correctness > and this obviously does. > > > > Is it true for Module level Metadata and not only for instruction attached > one? > > > There are examples of module-level metadata that impact the correctness of > the generated code in the LangRef today: > > http://llvm.org/docs/LangRef.html#module-flags-metadata > > http://llvm.org/docs/LangRef.html#objective-c-garbage-collection-module-flags-metadata > > http://llvm.org/docs/LangRef.html#automatic-linker-flags-module-flags-metadata > http://llvm.org/docs/LangRef.html#c...

PR15447 <http://llvm.org/bugs/show_bug.cgi?id=15447> brings up that there is an inconsistency both within LangRef and between LangRef and the implementation regarding what is an allowed return type. LangRef says: "The return type of a function type is a first class type or a void type." <http://llvm.org/docs/LangRef.html#id14> and also, contrarily, "<returntype>‘ is any type exce...

The LangRef page is missing a bunch of stuff, including documentation for all the LLVM instructions. The page ruins dorectory from Vector Types to llvm.readcyclecounter. Everything in-between is missing. -Dave

Hi, So the Variable Argument Handling Intrinsics section of the LangRef (http://llvm.org/docs/LangRef.html#variable-argument-handling-intrinsics) lists an example that segfaults. Try the following on x86_64: -- 8< -- define i32 @test(i32 %X, ...) { ; Initialize variable argument processing %ap = alloca i8* %ap2 = bitcast i8** %ap to i8* call void @llvm.va_s...

Hi, I don't find DIGlobalVariableExpression in langref. Should it be documented? Could anybody explain what it is? https://llvm.org/docs/LangRef.html In one ll file converted from bitcode, I mostly see something like this. !8273 = !DIGlobalVariableExpression(var: !8274, expr: !DIExpression()) Only one looks like this. !8945 = !DIGlobalVariableExpr...

> On Jul 31, 2015, at 10:56 AM, Eric Christopher <echristo at gmail.com> wrote: > > > On 30 July 2015 at 14:52, Daniel Sanders <Daniel.Sanders at imgtec.com <mailto:Daniel.Sanders at imgtec.com>> wrote: > > We will need a string serialization of the TargetTuple so that we can store it in the IR and read it back. > > Why does it have to be in the IR? If

...ess >> and this obviously does. >> >> >> >> Is it true for Module level Metadata and not only for instruction >> attached one? >> >> >> There are examples of module-level metadata that impact the correctness >> of the generated code in the LangRef today: >> >> http://llvm.org/docs/LangRef.html#module-flags-metadata >> >> http://llvm.org/docs/LangRef.html#objective-c-garbage-collection-module-flags-metadata >> >> http://llvm.org/docs/LangRef.html#automatic-linker-flags-module-flags-metadata >> http://...

http://llvm.org/docs/LangRef.html#i_inttoptr The 'inttoptr' instruction takes an integer<http://llvm.org/docs/LangRef.html#t_integer> value to cast, and a type to cast it to, which must be a pointer<http://llvm.org/docs/LangRef.html#t_pointer> type. The final example is: %Z = inttoptr <4 x i32> %G t...

[Bcc: Chris Lattner, who's listed in the "Written by"; the doc doesn't have a maintainer listed] I was reading http://llvm.org/docs/LangRef.html today and found some errors (or at least places where the text could be clearer). This is *NOT* an exhaustive reading; I'm just reporting the bugs I found in a casual reading of the intro and skimming the rest. I'm operating on the theory that reporting even a small number of errata is...

Hi all, There might be a simple error in the LLVM reference manual. The example for sext instruction: %X = sext i8 -1 to i16 ; yields i16 :65535 %X should yield i16: -1, as opposed to 65535. Here is the simple patch (also attached): Index: docs/LangRef.rst =================================================================== --- docs/LangRef.rst (revision 184496) +++ docs/LangRef.rst (working copy) @@ -5236,7 +5236,7 @@ .. code-block:: llvm - %X = sext i8 -1 to i16 ; yields i16 :65535 + %X = sext i8 -1 to i16...

The page looks ok to me... You are talking about this page, right? http://llvm.org/docs/LangRef.html -Tanya On Tue, 10 Jun 2008, David Greene wrote: > The LangRef page is missing a bunch of stuff, including documentation > for all the LLVM instructions. > > The page ruins dorectory from Vector Types to llvm.readcyclecounter. > Everything in-between is missing. > >...