search for: t_vector

Displaying 5 results from an estimated 5 matches for "t_vector".

Did you mean: _vector
2008 Jan 05
0
[LLVMdev] Calling functions across modules. And those pesky vectors!
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
2008 Jun 18
1
[LLVMdev] [PATCH] Insert a missing comma in documentation
...f.html @@ -1045,7 +1045,7 @@ classifications:</p> <td><a href="#t_integer">integer</a>, <a href="#t_floating">floating point</a>, <a href="#t_pointer">pointer</a>, - <a href="#t_vector">vector</a> + <a href="#t_vector">vector</a>, <a href="#t_struct">structure</a>, <a href="#t_array">array</a>, <a href="#t_label">label</a>.
2017 Nov 29
3
RFC: Adding 'no-overflow' keyword to 'sdiv'\'udiv' instructions
...""""" The '``udiv``' instruction returns the quotient of its two operands. Arguments: """""""""" The two arguments to the '``udiv``' instruction must be :ref:`integer <t_integer>` or :ref:`vector <t_vector>` of integer values. Both arguments must have identical types. Semantics: """""""""" The value produced is the unsigned integer quotient of the two operands. Note that unsigned integer division and signed integer division are distinct operatio...
2008 Jan 04
7
[LLVMdev] Calling functions across modules. And those pesky vectors!
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
2011 May 24
1
[LLVMdev] LLVM evaluation
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)