[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

https://bugs.kde.org/show_bug.cgi?id=375839 --- Comment #11 from Julian Seward --- Uh, I thought I fixed it pretty comprehensively in r3344. Anyway, can you get me please a copy of the basic block that contains the failing address? at 0xCC33BF:

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

https://bugs.kde.org/show_bug.cgi?id=375839 --- Comment #10 from Ronald S. Bultje --- We're still seeing the issue in FFmpeg. This is valgrind r16297 with vex r3344. ==15422== Memcheck, a memory error detector ==15422== Copyright (C) 2002-2015, and GNU GPL'd, by Julian

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

https://bugs.kde.org/show_bug.cgi?id=375839 Julian Seward changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

https://bugs.kde.org/show_bug.cgi?id=375839 --- Comment #8 from Julian Seward --- VEX r3335 further improves the situation a bit. I would be interested to hear if this makes it possible to run these problematic cases without the workaround in comment #4 (the use of

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

https://bugs.kde.org/show_bug.cgi?id=375839 --- Comment #7 from Julian Seward --- (In reply to Julian Seward from comment #1) > VEX has a very poor (verbose) translation for such instructions [..] VEX r3331 somewhat improves this, reducing the size of the generated code to

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

https://bugs.kde.org/show_bug.cgi?id=375839 --- Comment #6 from Eugene --- proposed WA with --vex-guest-max-insns=25 worked for me Thanks -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

https://bugs.kde.org/show_bug.cgi?id=375839 Julian Seward changed: What|Removed |Added CC||rsbul...@gmail.com ---

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

https://bugs.kde.org/show_bug.cgi?id=375839 --- Comment #4 from Julian Seward --- I should add: as a workaround, you can try specifying --vex-guest-max-insns=25 and if that still doesn't work, lowering the value towards zero. You shouldn't go below about 10. Lower values

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

https://bugs.kde.org/show_bug.cgi?id=375839 Eugene changed: What|Removed |Added CC||o1o2o3o...@gmail.com -- You

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

https://bugs.kde.org/show_bug.cgi?id=375839 Julian Seward changed: What|Removed |Added CC||nagendra.g...@gmail.com ---

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

https://bugs.kde.org/show_bug.cgi?id=375839 Julian Seward changed: What|Removed |Added CC||nmanj...@pretaktovanie.sk ---

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

https://bugs.kde.org/show_bug.cgi?id=375839 --- Comment #1 from Julian Seward --- Yes, VEX has a very poor (verbose) translation for such instructions and generates huge amounts of code, which breaks the JIT. We should fix this somehow. -- You are receiving this mail because:

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

https://bugs.kde.org/show_bug.cgi?id=375839 Jacek Czaja changed: What|Removed |Added CC||jacek.cz...@intel.com --