matthew.sel...@twosigma.com said:
> Sounds good. Will you rip the entire thing out in 1-shot, or in chunks?
> Will you remove the "waf configure --disable-fuzz" option entirely or
> leave some sort of backwards-compatible option?
I was going to do it in 1-shot. There aren't any obvious half-w
On Sun, Jun 23, 2024 at 09:39:17PM -0700, Hal Murray via devel wrote:
> Coverity got a little smarter and now reports a couple of cases of
> INTEGER_OVERFLOW in code that hasn't changed in a long time.
>
> One of them is in the clock fuzzing code. I propose to eliminate that
> feature.
>
> Any
Mark Atwood via devel :
> On Sun, Nov 24, 2019, at 19:32, Hal Murray via devel wrote:
> >
> > e...@thyrsus.com said:
> > > If we don't see any evidence of beat-induced quantization, I'm willing to
> > > say
> > > we drop this code.
> >
> > How about adding a --disable-fuzz configure option so w
Gary E. Miller via devel :
> Is there an existing patch to remove the fuzzing?
There is not. See my reply to Mark.
--
http://www.catb.org/~esr/";>Eric S. Raymond
signature.asc
Description: PGP signature
___
devel mailing list
devel@n
On 11/24/19 3:41 AM, Hal Murray via devel wrote:
> rlaa...@wiktel.com said:
>> I can build from git or with whatever patches, if needed. If something is
>> wrong with this clock fuzzing code, I'd love to help get to the bottom of it,
>> but this doesn't seem like the sort of thing I can sort out by
On Sun, Nov 24, 2019, at 19:32, Hal Murray via devel wrote:
>
> e...@thyrsus.com said:
> > If we don't see any evidence of beat-induced quantization, I'm willing to
> > say
> > we drop this code.
>
> How about adding a --disable-fuzz configure option so we can experiment
> without breaking the
e...@thyrsus.com said:
> If we don't see any evidence of beat-induced quantization, I'm willing to say
> we drop this code.
How about adding a --disable-fuzz configure option so we can experiment
without breaking the default case.
Or maybe a runtime configure option.
Early Raspberr
Yo Eric!
On Sun, 24 Nov 2019 08:55:53 -0500
"Eric S. Raymond via devel" wrote:
> We have pretty good visualization tools these days. Gary, you know
> best what normal perfornance looks like under ntpviz. Would you be
> willing to patch-disable fuzzing and see if that induces any
> suspicious-l
Eric S. Raymond via devel writes:
> If we don't see any evidence of beat-induced quantization, I'm willing
> to say we drop this code.
Please don't invent gobbledeegok terminology. "Beat-induced
quantization" is completely devoid of meaning. Again, what we're
talking about is dithering and it is
Hal Murray via devel :
> I'm tempted to rip out that stuff. I haven't quite convinced myself that it
> isn't doing something important. Eric?
The clock fuzzing? It's an interesting question. I've thought about it.
I'm doubtful myself. The obvious motivation would be to avoid beat
effects fro
10 matches
Mail list logo
