https://bugs.kde.org/show_bug.cgi?id=405782
--- Comment #12 from Julian Seward <jsew...@acm.org> --- Sorry to be slow getting to this, and thanks to Philippe for chasing it. Yes .. it looks like the problem was caused by a very verbose translation for the VPSHUFB instruction, applied to YMM registers. As Philippe says, that's something I fixed a few months back. > Do you still think the buffer sizes should be hard-coded though? A good question. The VEX compilation pipeline is "protected" by the fact that it will only include up to 50 instructions (with default settings) into a superblock. So even an infinitely long input basic block will not cause infinite memory use in the JIT, since it will be compiled in 50-instruction sections. It's just unfortunate that the translation of VPSHUFB in this case was so bad that the JIT overran the fixed working space. -- You are receiving this mail because: You are watching all bug changes.
