I guess you didn't see the reply since you weren't CC'ed explicitly: On Mon, Apr 7, 2014 at 9:53 AM, Sven Panne <[email protected]> wrote:
> I've never heard of that flag, and I'm quite sure that from a V8 POV, it > is OK to remove it. > I haven't heard of that flag before either, and I'm pretty sure that V8 doesn't use it. Replacing Math.random() with a deterministic pseudo-RNG can make a lot of sense to reduce benchmark flakiness, but that can easily be done in JavaScript (assuming that's what this flag used to do). On Tue, Apr 8, 2014 at 9:10 PM, Peter Kasting <[email protected]> wrote: > On Fri, Apr 4, 2014 at 3:16 PM, Peter Kasting <[email protected]> wrote: > >> Hi folks, >> >> I'm trying to track down whether --no-js-randomness is used anymore. The >> only use in the Chromium tree is in perftracker, which I've been told is >> unused. >> >> The effect of this flag is to register the v8 playback extension. >> >> Does anyone still use this? >> > > Having not heard anything, in a few days I'll remove this flag. > > Please respond soon if you do actually need this flag preserved for some > reason. > > PK > > -- > -- > v8-dev mailing list > [email protected] > http://groups.google.com/group/v8-dev > --- > You received this message because you are subscribed to the Google Groups > "v8-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
