Displaying 20 results from an estimated 66 matches for "letz".
Did you mean:
let
2010 Jun 03
1
[LLVMdev] Generating Floating point constants
> ------------------------------
>
> Message: 4
> Date: Wed, 2 Jun 2010 11:07:39 -0700
> From: Dale Johannesen <dalej at apple.com>
> Subject: Re: [LLVMdev] Generating Floating point constants
> To: St?phane Letz <letz at free.fr>
> Cc: llvmdev at cs.uiuc.edu
> Message-ID: <AEC895CC-E887-4329-8743-FA606BD401F6 at apple.com>
> Content-Type: text/plain; charset=iso-8859-1
>
>
> On Jun 2, 2010, at 11:05 AMPDT, St?phane Letz wrote:
>>>>
>>>>> and you d...
2010 May 29
2
[LLVMdev] Vectorized LLVM IR
...ure. Does it work better if you use
> something smaller like <4 x float>?
>
> Besides that, I don't see any obvious issues.
>
> -Eli
You are right yes. The code works faster with <4 x float> types, with still works a bit slower than the scalar version.
Stéphane Letz
2010 Jun 02
3
[LLVMdev] Generating Floating point constants
Le 2 juin 2010 à 12:21, Eli Friedman a écrit :
> On Wed, Jun 2, 2010 at 2:59 AM, Stéphane Letz <letz at free.fr> wrote:
>> Hi,
>>
>> We need to generate "Floating point constants" in our code. In http://llvm.org/docs/LangRef.html it is explained that FP has to follow special encoding rules to be handled by LLVM later one (hexadecimal coding...)
>>
&g...
2010 May 29
0
[LLVMdev] Vectorized LLVM IR
On Sat, May 29, 2010 at 1:23 AM, Stéphane Letz <letz at grame.fr> wrote:
>>
>> <32 x float> takes up 8 SSE registers; you're likely running into
>> issues with register pressure. Does it work better if you use
>> something smaller like <4 x float>?
>>
>> Besides that, I don't see an...
2013 Jul 16
4
[LLVMdev] General strategy to optimize LLVM IR
...mization code does not produce code as fast as the one produced with clang -03 anymore. Moreover the new vectorizations passes are still not working.
It there a recommended way to add -O1/-O2/-O3 kind of optimizations on LLVM IR code? Any code to look at beside the opt.cpp tool?
Thanks.
Stéphane Letz
2013 Jul 16
0
[LLVMdev] General strategy to optimize LLVM IR
On Tue, Jul 16, 2013 at 8:16 AM, Stéphane Letz <letz at grame.fr> wrote:
> Hi,
>
> Our DSL emit sub-optimal LLVM IR that we optimize later on (LLVM IR ==> LLVM IR) before dynamically compiling it with the JIT. We would like to simply follow what clang/clang++ does when compiling with -O1/-O2/-O3 options. Our strategy up to now...
2013 Jul 05
2
[LLVMdev] Enabling vectorization with LLVM 3.3 for a DSL emitting LLVM IR
Le 5 juil. 2013 à 17:23, Arnold Schwaighofer <aschwaighofer at apple.com> a écrit :
>
> On Jul 5, 2013, at 9:50 AM, Stéphane Letz <letz at grame.fr> wrote:
>
>>
>> Le 5 juil. 2013 à 04:11, Tobias Grosser <tobias at grosser.es> a écrit :
>>
>>> On 07/04/2013 01:39 PM, Stéphane Letz wrote:
>>>> Hi,
>>>>
>>>> Our DSL can generate C or directly gene...
2010 Jun 02
2
[LLVMdev] Generating Floating point constants
...in our code. In http://llvm.org/docs/LangRef.html it is explained that FP has to follow special encoding rules to be handled by LLVM later one (hexadecimal coding...)
Is there any code available in LLVM to handle this kind of "standard float to LLVM float" conversion?
Thanks.
Stéphane Letz
2010 Jun 02
0
[LLVMdev] Generating Floating point constants
On Jun 2, 2010, at 3:28 AMPDT, Stéphane Letz wrote:
>
> Le 2 juin 2010 à 12:21, Eli Friedman a écrit :
>
>> On Wed, Jun 2, 2010 at 2:59 AM, Stéphane Letz <letz at free.fr> wrote:
>>> Hi,
>>>
>>> We need to generate "Floating point constants" in our code. In http://llvm.org/docs/Lan...
2013 Jul 05
2
[LLVMdev] Enabling vectorization with LLVM 3.3 for a DSL emitting LLVM IR
Le 5 juil. 2013 à 04:11, Tobias Grosser <tobias at grosser.es> a écrit :
> On 07/04/2013 01:39 PM, Stéphane Letz wrote:
>> Hi,
>>
>> Our DSL can generate C or directly generate LLVM IR. With LLVM 3.3, we can vectorize the C produced code using clang with -O3, or clang with -O1 then opt -O3 -vectorize-loops. But the same program generating LLVM IR version cannot be vectorized with opt -O3 -v...
2013 Jul 18
2
[LLVMdev] LLVM 3.3 JIT code speed
...targetOptions.NoNaNsFPMath = true;
targetOptions.GuaranteedTailCallOpt = true;
builder.setTargetOptions(targetOptions);
TargetMachine* tm = builder.selectTarget();
fJIT = builder.create(tm);
if (!fJIT) {
return false;
}
….
Any idea?
Thanks.
Stéphane Letz
2013 Jul 05
0
[LLVMdev] Enabling vectorization with LLVM 3.3 for a DSL emitting LLVM IR
On Jul 5, 2013, at 9:50 AM, Stéphane Letz <letz at grame.fr> wrote:
>
> Le 5 juil. 2013 à 04:11, Tobias Grosser <tobias at grosser.es> a écrit :
>
>> On 07/04/2013 01:39 PM, Stéphane Letz wrote:
>>> Hi,
>>>
>>> Our DSL can generate C or directly generate LLVM IR. With LLVM 3.3, we c...
2010 Jun 02
0
[LLVMdev] Generating Floating point constants
On Wed, Jun 2, 2010 at 2:59 AM, Stéphane Letz <letz at free.fr> wrote:
> Hi,
>
> We need to generate "Floating point constants" in our code. In http://llvm.org/docs/LangRef.html it is explained that FP has to follow special encoding rules to be handled by LLVM later one (hexadecimal coding...)
>
> Is there any co...
2010 Jun 02
1
[LLVMdev] Generating Floating point constants
Le 2 juin 2010 à 19:48, Dale Johannesen a écrit :
>
> On Jun 2, 2010, at 3:28 AMPDT, Stéphane Letz wrote:
>
>>
>> Le 2 juin 2010 à 12:21, Eli Friedman a écrit :
>>
>>> On Wed, Jun 2, 2010 at 2:59 AM, Stéphane Letz <letz at free.fr> wrote:
>>>> Hi,
>>>>
>>>> We need to generate "Floating point constants" in our...
2010 May 28
3
[LLVMdev] Vectorized LLVM IR
...x float> kind of types), then compiling the code to SSE on a 64 bits machine. Right now the equivalent code in scalar mode sill outperform the SSE one.
What is the quality of the SSE support in X86 LLVL backend? Are they any specific things to be aware of to improve the speed?
Thanks
Stéphane Letz
2013 Jul 18
2
[LLVMdev] LLVM 3.3 JIT code speed
Le 18 juil. 2013 à 19:07, Eli Friedman <eli.friedman at gmail.com> a écrit :
> On Thu, Jul 18, 2013 at 9:07 AM, Stéphane Letz <letz at grame.fr> wrote:
>> Hi,
>>
>> Our DSL LLVM IR emitted code (optimized with -O3 kind of IR ==> IR passes) runs slower when executed with the LLVM 3.3 JIT, compared to what we had with LLVM 3.1. What could be the reason?
>>
>> I tried to play with Tar...
2013 Jul 18
0
[LLVMdev] LLVM 3.3 JIT code speed
On Thu, Jul 18, 2013 at 9:07 AM, Stéphane Letz <letz at grame.fr> wrote:
> Hi,
>
> Our DSL LLVM IR emitted code (optimized with -O3 kind of IR ==> IR passes) runs slower when executed with the LLVM 3.3 JIT, compared to what we had with LLVM 3.1. What could be the reason?
>
> I tried to play with TargetOptions without any...
2010 Jun 15
3
[LLVMdev] Adding fields in a already built type? (2)
Le 15 juin 2010 à 21:14, Chris Lattner a écrit :
>
> On Jun 15, 2010, at 11:51 AM, Stéphane Letz wrote:
>
>>> Nope, types are immutable once created. The only thing you can do is "refine" opaque types to other types. There is a section in the programmer's manual on this:
>>> http://llvm.org/docs/ProgrammersManual.html#TypeResolve
>>>
>>>...
2010 Jun 14
2
[LLVMdev] Adding fields in a already built type?
Hi,
We build a type with StructType::get(fModule->getContext(), fDspFields, false); with a fDspFields (std::vector<const llvm::Type*> fDspFields;) that is not yet completely known when we have to build the type. It is possible to add fields in a already build type?
Thanks
Stéphane Letz
2013 Jul 05
0
[LLVMdev] Enabling vectorization with LLVM 3.3 for a DSL emitting LLVM IR
On Jul 5, 2013, at 10:43 AM, Stéphane Letz <letz at grame.fr> wrote
>
> 1) "entry" block is the first block of the function right?
Yes.
>
> 2) do you mean *all* "alloca" in a function always have to be in the fist entry block?
If you want them converted into ssa variables early on, yes.