Re: [Valgrind-developers] Valgrind errors on PPC Power9 workloads

[Ivo R. <iv...@iv...>]

> From the comments in the code, it doesn't look like increasing the 15000
> is a viable option.

Actually this limit is somewhat arbitrary.
For register live ranges, type Short is used but only because invalid
start/end range is indicated with -2.
The rest of negative range is actually unused.
I think this can be easily changed to UShort instead, and the limit
raised to 62000, for example.

I can send you a patch if you are interested and willing to try it.

>  It appears that something is just generating too
> much stuff. I am wondering if anyone can give me some idea what is going
> on here.  It all appears to be architecture independent code.  Any
> suggestions on how to go about debugging this would be helpful.  Thanks.

Dump the information what the VEX JIT is doing.
1) Start with --trace-flags=10000000 --trace-notbelow=0
>From the last block dumped, note the SB number.
2) Refine with --trace-flags=11111100 --trace-notbelow=<SB-1>
You'll have relatively short dump with very useful information.

I.