aboutsummaryrefslogtreecommitdiffstats
path: root/gdbstub/user-target.c
diff options
context:
space:
mode:
authorAlex Bennée <alex.bennee@linaro.org>2024-03-05 12:09:37 +0000
committerAlex Bennée <alex.bennee@linaro.org>2024-03-06 12:35:09 +0000
commit13ddcf0a7a52ce17c836edbe6fc161a40269ce13 (patch)
treeb47f1e43e807add18e4e56f95679ae7be9ed472d /gdbstub/user-target.c
parentMerge tag 'pull-target-arm-20240305' of https://git.linaro.org/people/pmaydell/qemu-arm into staging (diff)
downloadqemu-13ddcf0a7a52ce17c836edbe6fc161a40269ce13.tar.xz
qemu-13ddcf0a7a52ce17c836edbe6fc161a40269ce13.zip
tests: bump QOS_PATH_MAX_ELEMENT_SIZE again
We "fixed" a bug with LTO builds with 100c459f194 (tests/qtest: bump up QOS_PATH_MAX_ELEMENT_SIZE) but it seems it has triggered again. The array is sized according to the maximum anticipated length of a path on the graph. However, the worst case for a depth-first search is to push all nodes on the graph. So it's not really LTO, it depends on the ordering of the constructors. Lets be more assertive raising QOS_PATH_MAX_ELEMENT_SIZE to make it go away again. Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1186 (again) Reviewed-by: Thomas Huth <thuth@redhat.com> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Message-Id: <20240305121005.3528075-2-alex.bennee@linaro.org>
Diffstat (limited to 'gdbstub/user-target.c')
0 files changed, 0 insertions, 0 deletions