diff options
author | Richard Henderson | 2018-10-22 20:16:23 +0200 |
---|---|---|
committer | Peter Maydell | 2018-10-23 11:12:46 +0200 |
commit | 3ebee3b191e755d3f7311a6a62eea5c9628b221b (patch) | |
tree | 2bd1549ce5e0a97ad8300b867cf786d3c1299357 /hw/vfio/platform.c | |
parent | Merge remote-tracking branch 'remotes/vivier2/tags/linux-user-for-3.1-pull-re... (diff) | |
download | qemu-3ebee3b191e755d3f7311a6a62eea5c9628b221b.tar.gz qemu-3ebee3b191e755d3f7311a6a62eea5c9628b221b.tar.xz qemu-3ebee3b191e755d3f7311a6a62eea5c9628b221b.zip |
osdep: Work around MinGW assert
In several places we use assert(FEATURE), and assume that if FEATURE
is disabled, all following code is removed as unreachable. Which allows
us to compile-out functions that are only present with FEATURE, and
have a link-time failure if the functions remain used.
MinGW does not mark its internal function _assert() as noreturn, so the
compiler cannot see when code is unreachable, which leads to link errors
for this host that are not present elsewhere.
The current build-time failure concerns 62823083b8a2, but I remember
having seen this same error before. Fix it once and for all for MinGW.
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-id: 20181022181623.8810-1-richard.henderson@linaro.org
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Diffstat (limited to 'hw/vfio/platform.c')
0 files changed, 0 insertions, 0 deletions