On 11/6/24 09:26, Peter Maydell wrote:
On Wed, 6 Nov 2024 at 17:21, Pierrick Bouvier
<pierrick.bouv...@linaro.org> wrote:
I noticed by --enable-debug in configure is a combination of enabling
checks (enable-debug-tcg + graph + mutex), and deactivating optimizations.
Would it be worth keeping the optimizations and runtime checks instead?
This way, there would be no more "timeout" issue.
I'm not sure which added value we get from O0, except for debugging
locally QEMU.
"Debugging locally QEMU" is exactly what --enable-debug is intended for...
Yes...
but it seems like we take it for "enable debug checks" in CI as well and
it impacts runtime, because optimizations are deactivated. I think I've
not been the only one confused about this.
So my point is that we should maybe differentiate the two use cases at
configure level.
--enable-debug and
--enable-runtime-checks (or something more explicit)
thanks
-- PMM
