Displaying 5 results from an estimated 5 matches for "mendis1989".
2017 Oct 03
2
Changing Alignment of global variables in LLVM
If I know for sure I am accessing 32 byte chunks at a time, how can I go
about changing the alignment of @u?
Should I use DataLayout's reset method? I couldn't find a method to change
alignment of one global variable.
Thanks
On Tue, Oct 3, 2017 at 6:34 PM, Matthias Braun <mbraun at apple.com> wrote:
> The effective alignment is part of the load and store operations. Updating
2016 Sep 03
2
llc error
I updated to the latest revision and now llvm does not build and quits
cmake with
CMake Error at cmake/modules/LLVMProcessSources.cmake:83 (message):
Found unknown source file
../llvm-revec/lib/CodeGen/MachineFunctionAnalysis.cpp
Please update
../llvm-revec/lib/CodeGen/CMakeLists.txt
Thanks
On Sat, Sep 3, 2016 at 2:09 AM, Craig Topper <craig.topper at gmail.com> wrote:
>
2017 Aug 21
2
Vectorization in LLVM x86 backend
I isolated the LLVM IR and the X86 instructions emitted for the function
and are attached herewith and it is clearly emitting vector instructions. I
am having a hard time figuring out where the vector instructions are
formulated. For sure SLP and Loop vectorizer is not doing anything.
On Mon, Aug 21, 2017 at 11:56 AM, Craig Topper <craig.topper at gmail.com>
wrote:
> The X86 backend
2016 Oct 13
2
Loop Unrolling Fail in Simple Vectorized loop
...> }
>
>
> The unroller cannot compute the backedge taken count. Therefore, it seems
> like the problem is not with the range of "count", can't the unroller
> compute it as (- 1 + %count / 4)?
>
> On Wed, Oct 12, 2016 at 11:28 PM, Charith Mendis <
> char.mendis1989 at gmail.com> wrote:
>
>> Thanks for the explanation. But I am a little confused with the following
>> fact. Can't LLVM keep vectorizable_elements as a symbolic value and convert
>> the loop to say;
>>
>> for(unsigned i = 0; i < vectorizable_elements ; i...
2016 Oct 13
2
Loop Unrolling Fail in Simple Vectorized loop
Thanks for the explanation. But I am a little confused with the following
fact. Can't LLVM keep vectorizable_elements as a symbolic value and convert
the loop to say;
for(unsigned i = 0; i < vectorizable_elements ; i += 2){
//main loop
}
for(unsigned i=0 ; i < vectorizable_elements % 2; i++){
//fix up
}
Why does it have to reason about the range of vectorizable_elements? Even