search for: load25

...nstCombiner needs use cost model to decide whether perform optimization or not. Without cost model from TargetTransformInfo, aggressively optimizing IR in vector types according to the number of bits demanded may lead to scalarization of vector operations. For example, if the input IR is: %wide.load25 = load <32 x i8>, <32 x i8>* %231, align 1 %232 = zext <32 x i8> %wide.load25 to <32 x i16> %233 = mul nuw nsw <32 x i16> %232, %164 ... %237 = trunc <32 x i16> %233 to <32 x i8> store <32 x i8> %237, <32 x i8>* %236, align 1 ICE: Eva...

...Mehdi > > Without cost model from TargetTransformInfo, aggressively > > optimizing > > IR in vector types according to the number of bits demanded may > > lead > > to scalarization of vector operations. For example, if the input IR > > is: > > > %wide.load25 = load <32 x i8>, <32 x i8>* %231, align 1 > > > %232 = zext <32 x i8> %wide.load25 to <32 x i16> > > > %233 = mul nuw nsw <32 x i16> %232, %164 > > > … > > > %237 = trunc <32 x i16> %233 to <32 x i8> > > >...

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

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

...load23 ALLOC LOAD > HAS_CONTENTS > ??? 0x7f73f0b16000->0x7f73f0b17000 at 0x07816000: load24a ALLOC LOAD > READONLY CODE HAS_CONTENTS > ??? 0x7f73f0b17000->0x7f73f0b17000 at 0x07817000: load24b ALLOC > READONLY CODE > ??? 0x7f73f0b2a000->0x7f73f0b2a000 at 0x07817000: load25 ALLOC READONLY > ??? 0x7f73f0d2a000->0x7f73f0d2b000 at 0x07817000: load26 ALLOC LOAD > HAS_CONTENTS > ??? 0x7f73f0d2b000->0x7f73f0d2c000 at 0x07818000: load27a ALLOC LOAD > READONLY CODE HAS_CONTENTS > ??? 0x7f73f0d2c000->0x7f73f0d2c000 at 0x07819000: load27b ALLOC &gt...

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 > > >

...0x7f73f0b16000 at 0x07815000: load23 ALLOC LOAD HAS_CONTENTS 0x7f73f0b16000->0x7f73f0b17000 at 0x07816000: load24a ALLOC LOAD READONLY CODE HAS_CONTENTS 0x7f73f0b17000->0x7f73f0b17000 at 0x07817000: load24b ALLOC READONLY CODE 0x7f73f0b2a000->0x7f73f0b2a000 at 0x07817000: load25 ALLOC READONLY 0x7f73f0d2a000->0x7f73f0d2b000 at 0x07817000: load26 ALLOC LOAD HAS_CONTENTS 0x7f73f0d2b000->0x7f73f0d2c000 at 0x07818000: load27a ALLOC LOAD READONLY CODE HAS_CONTENTS 0x7f73f0d2c000->0x7f73f0d2c000 at 0x07819000: load27b ALLOC READONLY CODE 0x7f73f0d...