files),
multiple instruction sequence, etc. If these are interesting to the
community, I will try to find time and submit. There are a lot of works to
make a proper patch than just making my hack. :)
Jun
On Tue, May 9, 2023 at 5:43 AM Peter Maydell
wrote:
> On Wed, 3 May 2023 at 17:35,
writes:
>
> > On Fri, 5 May 2023 at 01:23, Jun Sun wrote:
> >>
> >> Agree on the usefulness of generating the same test. That is the
> >> reason behind adding --randseed option. Once a seed is set, it
> >> always generates the same sequence of instructions
or generate a different fixed sequence.
Hope this clarifies things a little bit.
Jun
On Wed, May 3, 2023 at 10:05 AM Alex Bennée wrote:
>
> Jun Sun writes:
>
> > By default, risu currently does not generate random instruction
> sequences because it uses 0 as the random se
This mirrors the "--not-pattern" option and gives complete control over
group-based
instruction selection rules.
Signed-off-by: Jun Sun
---
risugen | 10 ++
1 file changed, 10 insertions(+)
diff --git a/risugen b/risugen
index f88c22a..f441f06 100755
--- a/risugen
+++
., union) for sequence
generation.
Signed-off-by: Jun Sun
---
risugen| 4 ++--
risugen_arm.pm | 1 +
risugen_loongarch64.pm | 1 +
risugen_m68k.pm| 1 +
risugen_ppc64.pm | 1 +
5 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/risugen b/risugen
By default, risu currently does not generate random instruction sequences
because it uses 0 as the random seed. This patch uses time() as random
seed and also introduces --randomseed option for deterministic sequence
generation.
0008-add-randseed-option-and-use-time-as-default-seed.patch
Descrip
