search for: 112358

I have noticed that when I iterate permutations of short vectors with the same seed, the cycle lengths are much shorter than I would expect by chance. For example: X <- 1:10 Xorig <- X start <- 112358 N <- 10 for (i in 1:N) { seed <- start + i for (j in 1:1000) { # Maximum cycle length to consider set.seed(seed) # Re-seed RNG to same initial state X <- sample(X) # Permute X and iterate if (all(X == Xorig)) { cat(sprintf("Seed:\t%d\tCycle: %d\n", se...

...pretty poor, so I cannot find such information. Removing the obsoleted class might be too aggressive. I am wondering if we can mark the class as deprecated [2] (seems C++14 feature required), or at least making a note on [3]. Thoughts? :-) [1] http://lists.llvm.org/pipermail/llvm-dev/2017-April/112358.html [2] http://josephmansfield.uk/articles/marking-deprecated-c++14.html [3] http://llvm.org/docs/CodeGenerator.html#selectiondag-scheduling-and-formation-phase -- Wei-Ren Chen (陳韋任) Homepage: https://people.cs.nctu.edu.tw/~chenwj

...AM, Boris Steipe <boris.steipe at utoronto.ca> wrote: > I have noticed that when I iterate permutations of short vectors with the > same seed, the cycle lengths are much shorter than I would expect by > chance. For example: > > X <- 1:10 > Xorig <- X > start <- 112358 > N <- 10 > > for (i in 1:N) { > seed <- start + i > for (j in 1:1000) { # Maximum cycle length to consider > set.seed(seed) # Re-seed RNG to same initial state > X <- sample(X) # Permute X and iterate > if (all(X == Xorig)) { > cat(sp...

I just recompiled a plain vanilla 2.4.28 kernel, and used the Shorewall.net kernel config as a guideline. For some reason, I get this: Nov 30 12:05:34 fw shorewall: Shorewall has detected the following iptables/netfilter capabilities: Nov 30 12:05:34 fw shorewall: NAT: Available Nov 30 12:05:34 fw shorewall: Packet Mangling: Available Nov 30 12:05:34 fw shorewall: Multi-port Match: