search for: const_vec

...<n x 4 x i32> zeroinitializer > %stridevec = mul <n x 4 x i32> stepvector, %widestep > %finalvec = add <n x 4 x i32> %widestart, %stridevec > ``` This is really fragile and confusing, and I agree with James, an intrinsic here would be *much* better. Something like %const_vec = <n x 4 x i32> @llvm.sve.constant_vector(i32 %start, i32 %step) cheers, --renato

...size is anyway. The only worry is about providing redundant information that could go stale and introduce bugs. I'm assuming the vectorizer will *have* to learn about the compulsory predication and build those vectors, or the back-end will have to handle them, and it can get ugly. >> %const_vec = <n x 4 x i32> @llvm.sve.constant_vector(i32 %start, i32 %step) > > This intrinsic matches the seriesvector instruction we original proposed. However, on reflection we didn't like how it allowed multiple representations for the same constant. Can you expand how this allows multip...

...ant information that could go > stale and introduce bugs. > > I'm assuming the vectorizer will *have* to learn about the compulsory > predication and build those vectors, or the back-end will have to > handle them, and it can get ugly. > > > >> %const_vec = <n x 4 x i32> @llvm.sve.constant_vector(i32 %start, i32 %step) > > > > This intrinsic matches the seriesvector instruction we original proposed. However, on reflection we didn't like how it allowed multiple representations for the same constant. > > Can yo...

Hi Renato, Sorry for the delay in responding. We've been busy rethinking some of our changes after the feedback we've received thus far (particularly from the devmeeting). The incremental patches will use our revised design(which should be less invasive), and I'll be updating our document to match. On 16/11/2016, 12:46, "Renato Golin" <renato.golin at linaro.org>