similar to: [LLVMdev] [PATCH] Insert a missing comma in documentation

Hi Jon, Please you'll want to submit patches as unified diffs and as attachments. I notice you're using Thunderbird, so I refer you to this tip: http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-January/011992.html Although this note doesn't apply to how you included your original patch (looks like you pasted it in), Thunderbird has default attachment handling settings which

Here is a patch containing all but one of the changes. I realized that the remainder/modulo discussion does indeed belongs to the srem instruction. The semantics of urem are obvious and need no further clarification. Best Regards, Jon 1572,1573c1572,1575 < notation (see below). Floating point constants must have a <a < href="#t_floating">floating point</a>

Danny wrote: I made a > simple function which was just supposed to multiply two 3 component > float vectors and return the result: "Vectors must have a power of two length (1, 2, 4, 8, 16 ...)." - http://llvm.org/docs/LangRef.html#t_vector > //Snip on: > VectorType *vType = VectorType::get(Type::FloatTy, 3); Nick

Introduction: We would like to add new keyword to 'sdiv'\'udiv' instructions i.e. 'no-overflow'. This is the updated solution devised in the discussion: http://lists.llvm.org/pipermail/llvm-dev/2017-October/118257.html The proposed keywords: "nof" stands for 'no-overflow' Syntax: <result> = sdiv nof <ty> <op1>,

To Whom This May Concern, Quite honestly, this email is a "long-shot in the dark" for me, since I'm not sure if this email account is still maintained or not. As I searched at google.com for "Samba Print Server" this afternoon, I was led to the USENIX site that contained this email link. I'm currently facing an issue which I'm hoping you can be of help. Our

Yes I know, I'm having problems with these tests because they violate the documentation. :) Micah From: Nadav Rotem [mailto:nrotem at apple.com] Sent: Wednesday, October 10, 2012 11:52 AM To: Villmow, Micah Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] Inconsistency in the LLVM docs Hi Micah, We need to fix the documentation here. We want to be able to convert vectors of integers to

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 to <4 x i8*>; yields truncation of vector G to four pointers The

Before I get started with more questions, thanks for the prompt reply on my last set question, that was much appreciated. First, I found references to lazy inling and optimizations for calling functions across modules, but I can't figure out how to do that. If I just take a Function* that I got out of one module and call it from the other, it doesn't work. What's the general

Hi, My organization is doing a technology comparison between GCC optimization/backend and LLVM infrastructures to select the best environment for our next product. Would you please help me to find answers on the following features’ list support availability inside current (or near future) LLVM implementation: 1. Intrinsic function support 2. Semi-standard embedded C types (complex, fractional)

Alireza, I have added full support for embedded C address spaces to the LLVM IR (see http://llvm.org/docs/LangRef.html#t_pointer). I have not added any support for the fractional types and their operators, though I think this would simply require adding the necessary intrinsics, which is one of the easier things to add to LLVM. Given that LLVM takes the approach of modeling these kinds

Christopher, Thank you for all the work :-) Regarding the regression testing, it is in our plan to contribute into LLVM. The current state of our project is not in the form that we can do this at this time though, but I'm hoping that we can get some minimal functionality into LLVM before LLVM 2.3 (at most LLVM 2.4) release. Looks like you have also (at least on your local project) taken

First off, most of my information about the integer representation in LLVM is from http://llvm.org/docs/LangRef.html#t_integer and I could use some things cleared up. First, I guess that smaller integer sizes, say, i1 (boolean) are stuffed into a full word size for the cpu it is compiled on (so 8bits, or 32 bits or whatever). What if someone made an i4 and compiled it on 32/64 bit windows/nix/bsd