search for: t0352

...experiencing: ; ModuleID = 'bugparam.ll' target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-n32" target triple = "thumbv7-none-linux-androideabi" define arm_aapcscc void @bar(i8* nocapture %.T0352, i16* nocapture %p) { L.entry: %0 = load i16* %p, align 2 %1 = bitcast i16 %0 to <2 x i8> %2 = getelementptr i16* %p, i32 1 %3 = load i16* %2, align 2 %4 = bitcast i16 %3 to <2 x i8> tail call arm_aapcscc void @zzz(<2 x i8> %1, <2 x i8> %4) ret void } declare...

...oduleID = 'bugparam.ll' > target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-n32" > target triple = "thumbv7-none-linux-androideabi" > > define arm_aapcscc void @bar(i8* nocapture %.T0352, i16* nocapture %p) { > L.entry: > %0 = load i16* %p, align 2 > %1 = bitcast i16 %0 to <2 x i8> > %2 = getelementptr i16* %p, i32 1 > %3 = load i16* %2, align 2 > %4 = bitcast i16 %3 to <2 x i8> > tail call arm_aapcscc void @zzz(<2 x i8> %1,...

Hi Sebastien, > Thanks for the quick answer, how do I know which type is legal/illegal with respect to calling convention ? the code generators are supposed to produce working code no matter what the parameter type is. The fact that the ARM ABI doesn't specify how <2 x i8> is passed just means that the code generators can pass it using whatever technique it feels like (since it

Hi Rotem, Thanks for the quick answer, how do I know which type is legal/illegal with respect to calling convention ? Best Regards Seb > -----Original Message----- > From: Rotem, Nadav [mailto:nadav.rotem at intel.com] > Sent: Thursday, July 05, 2012 11:21 AM > To: Sebastien DELDON-GNB; llvmdev at cs.uiuc.edu > Subject: RE: Vector argument passing abi for ARM ? > > The