Displaying 3 results from an estimated 3 matches for "merge_1".
2009 Feb 13
3
[LLVMdev] Modeling GPU vector registers, again (with my implementation)
...t;4 x float> %mul_1, <4 x float>* %r0
...
%add_1 = add <4 x float> %r3, %r4
; a store does not immediately happen here
%load_1 = load <4 x float>* %r0
; select the first two elements from the existing value,
; the last two elements from the newly generated value
%merge_1 = shufflevector <4 x float> %load_1,
<4 x float> %add_1,
<4 x i32> < i32 0, i32 1, i32 6, i32 7 >
; store the multiplexed value
store <4 x float> %merge_1, <4 x float>* %r0
After mem2reg:
%mul_1 = mu...
2009 Feb 13
0
[LLVMdev] Modeling GPU vector registers, again (with my implementation)
...t;* %r0
> ...
> %add_1 = add <4 x float> %r3, %r4
> ; a store does not immediately happen here
> %load_1 = load <4 x float>* %r0
>
> ; select the first two elements from the existing value,
> ; the last two elements from the newly generated value
> %merge_1 = shufflevector <4 x float> %load_1,
> <4 x float> %add_1,
> <4 x i32> < i32 0, i32 1, i32 6, i32 7 >
>
> ; store the multiplexed value
> store <4 x float> %merge_1, <4 x float>* %r0
>
&g...
2010 Aug 17
0
Merge xts
...t all the
time series in order and its corresponding data. I have tried several ways,
but it seems because my timestamps all differ, I am not able to use the
merge function.
If I use the merge function it puts the time series together but the data
are all in differing columns, for example ,
>merge_1<-merge(s1_predict.xts,s2_predict.xts,s3_predict.xts)
1990-03-27 02:00:00 6.142707 NA NA
1990-03-27 03:00:00 6.142707 NA NA
1990-03-27 04:00:00 NA 6.2688687 NA
1990-03-27 05:00:00 NA 5.93001...