search for: l394

...;h=ef45a2905bd8e3d920aa74d23a32fc0c169d9a57;hb=HEAD#l881 http://git.videolan.org/?p=x264.git;a=blob;f=common/x86/x86inc.asm;h=ef45a2905bd8e3d920aa74d23a32fc0c169d9a57;hb=HEAD#l590 http://git.videolan.org/?p=x264.git;a=blob;f=common/x86/dct-64.asm;h=c1aff843101f0081686f07ebe04908c7aa803e4a;hb=HEAD#l394 "portability": http://git.videolan.org/?p=x264.git;a=blob;f=common/x86/x86inc.asm;h=ef45a2905bd8e3d920aa74d23a32fc0c169d9a57;hb=HEAD#l88 -- Sean Silva > > A single assembler instruction, pseudo or otherwise, should represent a >> single instruction in the final output. Ev...

...power is back") command, and finds nothing that matches your UPS. Then it tries "load.on.delay" - same problem. It then finds the path for "shutdown.reboot", which is most likely mapped to this line: https://github.com/networkupstools/nut/blob/v2.7.2/drivers/tripplite-hid.c#L394 (IIRC it's the first match, otherwise it would be https://github.com/networkupstools/nut/blob/v2.7.2/drivers/tripplite-hid.c#L397 ) That sends a value of 10 (likely corresponding to the 10-second delay) to UPS.OutletSystem.Outlet.DelayBeforeReboot The fact that there is not a "UPS.Outlet...

On Oct 26, 2013, at 5:02 PM, Chris Lattner <clattner at apple.com> wrote: > On Oct 25, 2013, at 5:22 PM, Sean Silva <chisophugis at gmail.com> wrote: >> I’m not sure macros are a good analogy, but there are other pseudo-instructions that we’re not always able to reconstruct in disassembled code back to how the user wrote them. Or if we do, it’s purely via heuristic methods. I

Thanks for your help. From: Charles Lepple <clepple at gmail.com> Date: Mon, 18 Dec 2017 19:26:56 -0500 This may sound like an apples-to-oranges comparison, but we did uncover an issue with CyberPower UPSes where the delay values needed to be greater than or equal to 60 (seconds), since they were being rounded down to integer numbers of minutes internally: What was the largest