search for: exitvalue

https://bugzilla.samba.org/show_bug.cgi?id=1652 Summary: rsync --timeout=n -> if timeout occurs, exits with no exitvalue Product: rsync Version: 2.6.0 Platform: x86 OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: mtempels@townsville.nl QAContact:...

https://bugzilla.samba.org/show_bug.cgi?id=1652 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2004-09-18 10:16 ------- I get the proper exit-code 30 on timeout. Can you be

https://bugzilla.samba.org/show_bug.cgi?id=1652 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From wayned@samba.org 2005-03-18 19:52

...Int One(BitWidth,1); APInt A = cast<SCEVConstant>(getOperand(1))->getValue()->getValue(); APInt End = A.sge(One) ? (Range.getUpper() - One) : Range.getLower(); // The exit value should be (End+A)/A. APInt ExitVal = (End + A).udiv(A); ConstantInt *ExitValue = ConstantInt::get(SE.getContext(), ExitVal); In gdb, $6 = {BitWidth = 8, {VAL = 254, pVal = 0xfe}} (gdb) p ExitVal.isNegative() $7 = true (gdb) p ExitValue->dump() i8 -2 $8 = void It looks like whenever the value of ExitVal is greater than 128, ExitValue is going to be negative. This makes g...

...nce regression. I think after rL346397 LSR is not able to rewrite all the uses of %2 because phi node (%.lcssa) was not rewritten by indvars pass. Simple fix would be just returning back original check for SCEVType in lib/Transforms/Scalar/IndVarSimplify.cpp: - if (!isa<SCEVConstant>(ExitValue) && hasHardUserWithinLoop(L, Inst)) + if ((ExitValue->getSCEVType() >= scMulExpr) && hasHardUserWithinLoop(L, Inst)) Note, there is another bug opened for the mentioned patch: https://bugs.llvm.org/show_bug.cgi?id=39673, but it only fixes the problem when the SCEV expr...

...pass ScalarEvolution to analyze the loop trip count on my application. And I found a possible bug in the code, that is in function SCEVAddRecExpr::getNumIterationsInRange(), Line 2905: 2904 // The exit value should be (End+A)/A. 2905 APInt ExitVal = (End + A).udiv(A); 2906 ConstantInt *ExitValue = ConstantInt::get(ExitVal); The divide should be sdiv, right? otherwise, the ExitVal will be zero when A = -1 For example, for (int i = 15; i > 7; --i) {} the exit value should be 7 not zero. Also, I think we should consider the possible overflow situation, for example, for (uint7 i...

...if (e.getMessage().equals("Cannot connect: Connection refused")) { try { String rserveStartCommand = "R CMD Rserve --vanilla"; //do a blocking call to the shell command for starting Rserve int exitValue = Runtime.getRuntime().exec(rserveStartCommand).waitFor(); //if it returned success, try connecting again if (exitValue == 0) return new Rconnection(); //otherwise, Rserve is probably not installed...

...lks voiced general support, but with questions about why existing optimizations do not already catch this case. Deep dive by Wei Mi showed that the optimization is most likely not a clean-up of LSR sloppiness, but something new. Follow-up by myself confirmed that the redundancy eliminated the LoopExitValues pass exists in the original IR from Clang. As a next step, can we come to consensus on where the LoopExitValues optimization belongs? Regards, -steve

On Mon, Sep 21, 2015 at 11:13 AM, Wei Mi <wmi at google.com> wrote: > Maybe it can follow the "Delete dead loops" pass which is after > Induction Variable Simplification pass, so it will not affect existing > exitvalue rewriting optimization in Induction Variable Simplification > to find out and delete dead loops? > > Existing pass pipeline: > Loop-Closed SSA Form Pass > Loop Pass Manager > Induction Variable Simplification > Recognize loop idioms >...

...rithms failed to compute the trip count: 1. In SCEVAddRecExpr::getNumIterationsInRange(), as the loop stride is negative, the exit value expression will be zero: (Here A is the stride value) // The exit value should be (End+A)/A. APInt ExitVal = (End + A).udiv(A); ConstantInt *ExitValue = ConstantInt::get(ExitVal); 2. In Line 1953, the switch-case computes the trip count due to different Cond code. But in this case, as it exits on true, the slt is converted to sge, not switch-case for this condtion. 3. As the loop count is over 100, the Brute-Force algorithm also doent wo...

...quot; subj=system_u:system_r:logrotate_t:s0-s0:c0.c1023 key=(null) It is (obviously) a selinux problem, but I don't know what file or directory needs to be fixed. How to I find that out? I turned on verbose in /etc/cron.daily/logrotate: #!/bin/sh /usr/sbin/logrotate -v /etc/logrotate.conf EXITVALUE=$? if [ $EXITVALUE != 0 ]; then /usr/bin/logger -t logrotate "ALERT exited abnormally with [$EXITVALUE]" fi and am getting this (typical) message from logrotate daily: reading config file /etc/logrotate.conf including /etc/logrotate.d reading config file apcupsd reading config info...

I've noticed that there was an attempt to mitigate ExitValues problem in https://reviews.llvm.org/D12494 that went nowhere. Were there particular issues with that approach? -- Danila From: Philip Reames [mailto:listmail at philipreames.com] Sent: Saturday, August 10, 2019 02:05 To: Danila Malyutin <Danila.Malyutin at synopsys.com>; Finkel, Hal J. &lt...

...e(), as the loop stride is >> > negative, the exit value expression will be zero: (Here A is the stride >> > value) >> > >> > // The exit value should be (End+A)/A. >> > APInt ExitVal = (End + A).udiv(A); >> > ConstantInt *ExitValue = ConstantInt::get(ExitVal); >> > > Yes, that code path will fail for this example. > Why not improve this? We can change it into : APInt ExitVal = (End + A).sdiv(A); Surely we should take care of the range of this expression, maybe need extend the bitwidth of (End+...

...t: Re: [llvm-dev] How to best deal with undesirable Induction Variable Simplification? Wasn't aware of this patch. No, I don't see an obvious reason why it wasn't followed up on. Philip On 8/13/19 8:25 AM, Danila Malyutin wrote: I've noticed that there was an attempt to mitigate ExitValues problem in https://reviews.llvm.org/D12494<https://urldefense.proofpoint.com/v2/url?u=https-3A__reviews.llvm.org_D12494&d=DwMD-g&c=DPL6_X_6JkXFx7AXWqB0tg&r=VEV8gWVf26SDOqiMtTxnBloZmItAauQlSqznsCc0KxY&m=dG9EWNnpejxa8ub7_ajgnN50pG20wvSyA7WI9jWEv2Q&s=XRJmqJsGpSvBiRcYTKFYc_m94KM...

...So LSR could theoretically counteract undesirable Ind Var transformations but it's not implemented at the moment? I think I've managed to come up with a small reproducer that can also exhibit similar problem on x86, here it is: https://godbolt.org/z/_wxzut As you can see, when rewriteLoopExitValues is not disabled Clang generates worse code due to additional spills, because Ind Vars rewrites all exit values of 'a' to recompute it's value instead of reusing the value from the loop body. This requires extra registers for the new "a after the loop" value (since it's no...