Displaying 11 results from an estimated 11 matches for "load14".
Did you mean:
load1
2018 Jan 20
2
Non-Temporal hints from Loop Vectorizer
...x i32], [2048 x i32]* @b, i64 0, i64
%index
%1 = bitcast i32* %0 to <16 x i32>*
%wide.load = load <16 x i32>, <16 x i32>* %1, align 16, !tbaa !1
%8 = getelementptr inbounds [2048 x i32], [2048 x i32]* @c, i64 0, i64
%index
%9 = bitcast i32* %8 to <16 x i32>*
%wide.load14 = load <16 x i32>, <16 x i32>* %9, align 16, !tbaa !1
%16 = add nsw <16 x i32> %wide.load14, %wide.load
%20 = getelementptr inbounds [2048 x i32], [2048 x i32]* @a, i64 0, i64
%index
%21 = bitcast i32* %20 to <16 x i32>*
store <16 x i32> %16, <16 x i32>*...
2018 Jan 20
2
Non-Temporal hints from Loop Vectorizer
...64
> %index
> %1 = bitcast i32* %0 to <16 x i32>*
> %wide.load = load <16 x i32>, <16 x i32>* %1, align 16, !tbaa !1
> %8 = getelementptr inbounds [2048 x i32], [2048 x i32]* @c, i64 0, i64
> %index
> %9 = bitcast i32* %8 to <16 x i32>*
> %wide.load14 = load <16 x i32>, <16 x i32>* %9, align 16, !tbaa !1
> %16 = add nsw <16 x i32> %wide.load14, %wide.load
> %20 = getelementptr inbounds [2048 x i32], [2048 x i32]* @a, i64 0, i64
> %index
> %21 = bitcast i32* %20 to <16 x i32>*
> store <16 x i32>...
2018 Jan 20
0
Non-Temporal hints from Loop Vectorizer
...t; i64 %index
> %1 = bitcast i32* %0 to <16 x i32>*
> %wide.load = load <16 x i32>, <16 x i32>* %1, align 16, !tbaa !1
> %8 = getelementptr inbounds [2048 x i32], [2048 x i32]* @c, i64 0,
> i64 %index
> %9 = bitcast i32* %8 to <16 x i32>*
> %wide.load14 = load <16 x i32>, <16 x i32>* %9, align 16, !tbaa !1
> %16 = add nsw <16 x i32> %wide.load14, %wide.load
> %20 = getelementptr inbounds [2048 x i32], [2048 x i32]* @a, i64 0,
> i64 %index
> %21 = bitcast i32* %20 to <16 x i32>*
> store <16 x i32&g...
2018 Jan 21
0
Non-Temporal hints from Loop Vectorizer
...%0 to <16 x i32>*
>> %wide.load = load <16 x i32>, <16 x i32>* %1, align 16, !tbaa !1
>> %8 = getelementptr inbounds [2048 x i32], [2048 x i32]* @c, i64
>> 0, i64 %index
>> %9 = bitcast i32* %8 to <16 x i32>*
>> %wide.load14 = load <16 x i32>, <16 x i32>* %9, align 16, !tbaa !1
>> %16 = add nsw <16 x i32> %wide.load14, %wide.load
>> %20 = getelementptr inbounds [2048 x i32], [2048 x i32]* @a,
>> i64 0, i64 %index
>> %21 = bitcast i32* %20 to <16 x i32&g...
2018 Jan 20
0
Non-Temporal hints from Loop Vectorizer
On 20/01/2018 17:44, hameeza ahmed via llvm-dev wrote:
> Hello,
>
> My work deals with non-temporal loads and stores i found non-temporal
> meta data in llvm documentation but its not shown in IR.
>
> How to get non-temporal meta data?
llvm\test\CodeGen\X86\nontemporal-loads.ll shows how to create nt vector
loads in IR - is that what you're after?
Simon.
2018 Jan 20
2
Non-Temporal hints from Loop Vectorizer
Hello,
My work deals with non-temporal loads and stores i found non-temporal meta
data in llvm documentation but its not shown in IR.
How to get non-temporal meta data?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180120/7dd4ba6f/attachment.html>
2013 Jul 05
0
[LLVMdev] Enabling vectorization with LLVM 3.3 for a DSL emitting LLVM IR
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 -vectorize-loops. So our guess is that our generated LLVM IR lacks some
2013 Jul 04
3
[LLVMdev] Enabling vectorization with LLVM 3.3 for a DSL emitting LLVM IR
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 -vectorize-loops. So our guess is that our generated LLVM IR lacks some informations that are needed by the vectorization passes to
2018 Jan 29
1
Panic: data stack: Out of memory when allocating bytes
...at 0x0780e000: load12a ALLOC LOAD
> READONLY CODE HAS_CONTENTS
> ??? 0x7f73f0305000->0x7f73f0305000 at 0x0780f000: load12b ALLOC
> READONLY CODE
> ??? 0x7f73f030c000->0x7f73f030c000 at 0x0780f000: load13 ALLOC READONLY
> ??? 0x7f73f050b000->0x7f73f050c000 at 0x0780f000: load14 ALLOC LOAD
> HAS_CONTENTS
> ---Type <return> to continue, or q <return> to quit---
> ??? 0x7f73f050c000->0x7f73f050d000 at 0x07810000: load15a ALLOC LOAD
> READONLY CODE HAS_CONTENTS
> ??? 0x7f73f050d000->0x7f73f050d000 at 0x07811000: load15b ALLOC
> READONL...
2018 Jan 24
2
Panic: data stack: Out of memory when allocating bytes
On Wed, Jan 24, 2018 at 18:55:47 +0100, Thomas Robers wrote:
> Am 23.01.2018 um 20:07 schrieb Josef 'Jeff' Sipek:
> > On Tue, Jan 23, 2018 at 14:03:27 -0500, Josef 'Jeff' Sipek wrote:
> > > On Tue, Jan 23, 2018 at 18:21:38 +0100, Thomas Robers wrote:
...
> > > 1. Do you have any idea what the imap process was doing at the time of the
> > >
2018 Jan 25
0
Panic: data stack: Out of memory when allocating bytes
...04000->0x7f73f0305000 at 0x0780e000: load12a ALLOC LOAD
READONLY CODE HAS_CONTENTS
0x7f73f0305000->0x7f73f0305000 at 0x0780f000: load12b ALLOC
READONLY CODE
0x7f73f030c000->0x7f73f030c000 at 0x0780f000: load13 ALLOC READONLY
0x7f73f050b000->0x7f73f050c000 at 0x0780f000: load14 ALLOC LOAD
HAS_CONTENTS
---Type <return> to continue, or q <return> to quit---
0x7f73f050c000->0x7f73f050d000 at 0x07810000: load15a ALLOC LOAD
READONLY CODE HAS_CONTENTS
0x7f73f050d000->0x7f73f050d000 at 0x07811000: load15b ALLOC
READONLY CODE
0x7f73f050f000->...