Displaying 5 results from an estimated 5 matches for "curosity".
Did you mean:
curiosity
2006 Jan 23
3
Curosity on HTB
Hello members.
I wanted know if htb shapes download speed and upload speed too? i want to
give a client 128/64. so is it possible to give 128 download download speed
and 64 upload speed.I mean 2 way traffic control.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
2003 Feb 06
5
options(chmhelp = TRUE)
Hi all,
Here's a curosity I ran into since upgrading to 1.6.2 (precompiled
for Windows). When using the chm help I get the following warning. I saw
a recent post regarding this as a new warning (``dyn.load warning
message in R1.6.2 on Windows XP'' dated 1/28/03), but not in the context
of the help system. The wa...
2013 Dec 11
1
[LLVMdev] Float undef value propagation
...the floating point semantics of LLVM's IR, but
> suspect there might be such a case. A few cases worth thinking
> about: undef + max_float, undef + NAN (signaling or non-signalling).
> If someone more familiar with floating point knows better, please
> feel free to chime in.
Out of curosity, do we currently perform this transformation when -enable-unsafe-fp-math is specified (-ffast-math from Clang)?
-Hal
>
> On the other hand, the following transformation is definitely safe:
>
>
> define float @_Z1fv() #0 {
>
> entry:
>
> ret 2.000000e+00 }
> (un...
2013 Dec 10
0
[LLVMdev] Float undef value propagation
On 12/9/13 2:13 PM, Raoux, Thomas F wrote:
>
> Constant propagation pass generates constant expression when undef is
> used in float instructions instead of propagating the undef value.
>
> ; Function Attrs: nounwind
>
> define float @_Z1fv() #0 {
>
> entry:
>
> %add = fadd fast float undef, 2.000000e+00
>
> ret float %add
>
> }
>
> Becomes:
2013 Dec 09
4
[LLVMdev] Float undef value propagation
Constant propagation pass generates constant expression when undef is used in float instructions instead of propagating the undef value.
; Function Attrs: nounwind
define float @_Z1fv() #0 {
entry:
%add = fadd fast float undef, 2.000000e+00
ret float %add
}
Becomes:
; Function Attrs: nounwind
define float @_Z1fv() #0 {
entry:
ret float fadd (float undef, float 2.000000e+00)
}
Is it safe