search for: dst2

I have a simple script that sends one file to two locations on the same destination server. Here's the code: DEST="remotehost" SRC="/home/boss/application.conf" DST1="/home/user1/application.conf" DST2="/home/user2/application.conf" RSYNC1=`rsync -caW -e ssh $SRC $DEST:$DST1` RSYNC2=`rsync -caW -e ssh $SRC $DEST:$DST2` This runs every 5 minutes. What I'm seeing is the first location occasionally gets a *partial* file, but the second location never has a problem. There does not ap...

...| ----------- | | | | ------------ ------------ | | | | | DST1 | | DST2 | | | | | ----------- ----------- For example I want make NAT if packet destination is DST1 (network or PC) but not if destination is DST2. Thanks on advance.

Dear All, I am struggling with the following problem: I am given a NxN symmetric matrix P ( P[i,i]=0, i=1...N and P[i,j]>0 for i!=j) which stands for the relative distances of N points. I would like use it to get the coordinates of the N points in a 2D plane. Of course, the solution is not unique (given one solution, I can translate or rotate all the points by the same amount and generate

...%_tmp3 = call %rec6 @llvm.phx.divm.u16.rec6(i16 %_tmp1, i16 %_tmp2) has been lowered to t6: i16,i16 = llvm.phx.divm.u16 TargetConstant:i16<3778>, t2, t4 and the instruction I want to select also returns two values def divm16_pseudo : MyPseudoInst< (outs aNh_0_7:$dst, aNh_0_7:$dst2), (ins aNh_0_7:$src1, aNh_0_7:$src2)>; Both outs are i16. /Mikael

...ture I think we ought to have that isn't on the requirements >> list already, is that I think we should have a means to support rules >> with more than one match root. For example (using SelectionDAG patterns): >> (set $dst1:GPR32, (i32 (load $ptr:GPR64))) >> (set $dst2:GPR32, (i32 (load (add $ptr:GPR64 4)))) >> into: >> (set $tmp:GPR64, (v2s32 (load $ptr:GPR64))) >> (set $dst1, (extractelt $tmp:GPR64, 0)) >> (set $dst2, (extractelt $tmp:GPR64, 1)) >> Or something along those lines (such as fusing div/mod together). The >&gt...

https://bugzilla.samba.org/show_bug.cgi?id=11866 Bug ID: 11866 Summary: rsync fails (failed to re-stat) when using double fuzzy + link-dest on renamed files Product: rsync Version: 3.1.1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component:

...> One feature I think we ought to have that isn't on the requirements list already, is that I think we should have a means to support rules with more than one match root. For example (using SelectionDAG patterns): >>> (set $dst1:GPR32, (i32 (load $ptr:GPR64))) >>> (set $dst2:GPR32, (i32 (load (add $ptr:GPR64 4)))) >>> into: >>> (set $tmp:GPR64, (v2s32 (load $ptr:GPR64))) >>> (set $dst1, (extractelt $tmp:GPR64, 0)) >>> (set $dst2, (extractelt $tmp:GPR64, 1)) >>> Or something along those lines (such as fusing div/mod tog...

...(ins globaladdress:$global), >> "$dst=memd(#$global)", >> []>; >> >> let isPredicable = 1, mayLoad = 1, hasCtrlDep = 1, neverHasSideEffects = 1 in >> -def POST_LDrid : LDInstPI<(outs DoubleRegs:$dst, IntRegs:$dst2), >> +def POST_LDrid : LDInst2PI<(outs DoubleRegs:$dst, IntRegs:$dst2), >> (ins IntRegs:$src1, s4Imm:$offset), >> "$dst = memd($src1++#$offset)", >> [], >> @@ -895,64 +895,64 @@ def POST_LDrid : LDInstPI<(outs D...

...=200) jpeg(filename = "C:/fig1.jpg", width = 5, height = 4,pointsize = 12, quality = 100, bg = "white", res = NA) par(mfrow=c(1,2),plt=c(.15,.99,.15,.95),mgp=c(1.5,1,0),tcl=-.25,cex.axis=.8) dsn2.plot (x,y,xi=c(29,6),Omega=matrix(c(2580,458,458,84),2),alpha=c(5482940,-2120750)) dst2.plot(x,y, xi=c(29,6),Omega=matrix(c(2065,380,380,72),2),alpha =c(48,-13),df=10) dev.off() I've also tried using graphics.off(). Any help would be greatly appreciated? Thanks, Martin Heller [[alternative HTML version deleted]]

...CALL from call file for outgoing: Channel-${CHANNEL} -----) *same => n,Dial(DAHDI/g0/${contact_no},45)* same => n,Noop(***** DIALSTATUS-${DIALSTATUS}*****) same => n,hangup exten => h,1,NoOP(Call hangup === outgoing context) same => n,NoOP(calldate2=${CDR(calldate)},src2=${CDR(src)},dst2=${CDR(dst)}) same => n,NoOP(channel2=${CDR(channel)},dstchannel2=${CDR(dstchannel)}start2=${CDR(start)}) same => n,NoOP(end2=${CDR(end)},duration2=${CDR(duration)},billsec=${CDR(billsec)},disposition2=${CDR(disposition)}) [outgoing_ivrs] exten => s,1,Noop(----- Second LEG CALL from call f...

...Intrinsic<[llvm_any_ty], [llvm_i16_ty, llvm_i16_ty], [IntrNoMem]>; that I want to translate to the following instruction during instruction selection: def divm16_pseudo : MyPseudoInst< (outs aNh_0_7:$dst, aNh_0_7:$dst2), (ins aNh_0_7:$src1, aNh_0_7:$src2)>; So I've done a pattern the same way I've done for numerous other intrinsics (that returns simple types like i16/i32 etc): def : Pat<(int_phx_divm_u16 i16:$src1, i16:$src2), (divm16_pseudo $src1, $src2)>; But this doesn'...

...rec6(i16 %_tmp1, i16 %_tmp2) > > has been lowered to > > t6: i16,i16 = llvm.phx.divm.u16 TargetConstant:i16<3778>, t2, t4 > > and the instruction I want to select also returns two values > > def divm16_pseudo : MyPseudoInst< > (outs aNh_0_7:$dst, aNh_0_7:$dst2), > (ins aNh_0_7:$src1, aNh_0_7:$src2)>; > > Both outs are i16. > > /Mikael > The intrinsic itself should define multiple IR outputs rather than using any ty. I’m also not sure if tablegen currently supports patterns with multiple results -Matt

> On Nov 10, 2017, at 10:19 AM, Hal Finkel via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > On 11/10/2017 11:12 AM, Amara Emerson via llvm-dev wrote: >> Hi everyone, >> >> This RFC concerns the design and architecture of a generic machine instruction combiner/optimizer framework to be developed as part of the GISel pipeline. As we transition from

...mount -t tmpfs tmpfs mnt ln -s BLABLA mnt/test mkdir src ln -s /tmp/rsync_bug/mnt src/dir rsync -aHx --delete --numeric-ids src/ dst1 rm src/dir mkdir src/dir cp -a mnt/test src/dir/ rsync -aHx --delete --numeric-ids --link-dest /tmp/rsync_bug/dst1 src/ dst2 || echo RSYNC FAIL Output for me: buczek at theinternet:~$ sudo ./rsync-bug.sh + '[' -d /tmp/rsync_bug ']' + umount /tmp/rsync_bug/mnt + rm -rf /tmp/rsync_bug + mkdir /tmp/rsync_bug + cd /tmp/rsync_bug + mkdir mnt + mount -t tmpfs tmpfs mnt...

Hi, Is there a function in R that I can use to fit the data with skew t distribution? Speaking in detail, I first used the kernel density estimation to fit my data, then I drew the skew t using my specified location, scale, shape, and df to make it close to the kernel density. Now I want to get the parameter estimations of the skew t which give me the closet density to the kernel density.

...ting points. However, only NVPTX makes use of tblgen which removes some burder from the backend developer. I also think that a tblgen-based backend like NVPTX is easier to maintain in the long term. What do you think? 2) NAC uses the following statement form (for any given statement): dst1, dst2, ..., dstm <= op src1, src2, ..., srcn; which expresses an operation op with n source operands and m destination operands. Do you think that tblgen supports such form or should I sanitize it? 3) The NAC memory model uses separate address spaces per array. A general-use stack/heap might a...

...[llvm_i16_ty, llvm_i16_ty], >> [IntrNoMem]>; >> >> that I want to translate to the following instruction during instruction selection: >> >> def divm16_pseudo : MyPseudoInst< >> (outs aNh_0_7:$dst, aNh_0_7:$dst2), >> (ins aNh_0_7:$src1, aNh_0_7:$src2)>; >> >> So I've done a pattern the same way I've done for numerous other intrinsics (that returns simple types like i16/i32 etc): >> >> def : Pat<(int_phx_divm_u16 i16:$src1, i16:$src2), >> (divm...

...the same". The assert assumes that, if the sources are the same register then the destinations must be as well. My instructions look like this, however: %V2<def> = COPY %V6 %V6<def> = COPY %V2_LO (isNopCopy is called with src and dest of the first instruction switched.) So dst2 == src1 but src2 is a subregister of dst1. Is there some assumption that size(src) == size(dst)? This second COPY, with size(src) != size(dst) was generated in InstrEmitter::EmitSubregNode at // Create the extract_subreg machine instruction. So it's not out-of-tree code. Am I missing somethi...

...> [llvm_i16_ty, llvm_i16_ty], > [IntrNoMem]>; > > that I want to translate to the following instruction during instruction selection: > > def divm16_pseudo : MyPseudoInst< > (outs aNh_0_7:$dst, aNh_0_7:$dst2), > (ins aNh_0_7:$src1, aNh_0_7:$src2)>; > > So I've done a pattern the same way I've done for numerous other intrinsics (that returns simple types like i16/i32 etc): > > def : Pat<(int_phx_divm_u16 i16:$src1, i16:$src2), > (divm16_pseudo $src1, $src2)&...

...gt; >> has been lowered to >> >> t6: i16,i16 = llvm.phx.divm.u16 TargetConstant:i16<3778>, t2, t4 >> >> and the instruction I want to select also returns two values >> >> def divm16_pseudo : MyPseudoInst< >> (outs aNh_0_7:$dst, aNh_0_7:$dst2), >> (ins aNh_0_7:$src1, aNh_0_7:$src2)>; >> >> Both outs are i16. >> >> /Mikael >> > > The intrinsic itself should define multiple IR outputs rather than using any ty. But the intrinsic returns a record so in the input ll-file it is one result %_t...