|Re: [hatari-devel] fixing errors reported by GCC 10 -fanalyzer|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] fixing errors reported by GCC 10 -fanalyzer
- From: Thomas Huth <th.huth@xxxxxxxxx>
- Date: Wed, 13 May 2020 19:34:09 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1589391251; bh=8C3W66gawusjIuC5hq6bHLdoNrPrjgyNMnvzK0kBpYg=; h=Date:From:To:Subject:From; b=SB9hIxEaDrXbFCp9esJI6+H8I0Qu5xybPFA7duuC5dy6t1GFE2V/TQ+KVgEeW7u+U JSSIz8O2P54LO/43b9vPr8xBfPgjP7lV8ga4r0wXAcrGVuiydGE6I7hJV252hjVIuI 575+q88UcZUU9G9qKMfCaNg0w/kKoxr6IJDLDXRdUGEqFqTkreuSnGqOKXend3M3JB Z3rBqqjbAC0zuM2OaPz49uFyX7KRf5qv2MovstWFEJYbCY11e0gNdK/KPpO7myP0U3 ReShlvD/TaFudVTy6ISkQfx3/WRUxStFzpfu5Wf2KNypwqTGgphQ9A3vjI/7YBPTgW QqCwKemn5Jwqw==
Am Wed, 13 May 2020 18:59:19 +0200
schrieb Nicolas Pomarède <npomarede@xxxxxxxxxxxx>:
> Le 13/05/2020 à 18:49, Eero Tamminen a écrit :
> > If tester knows whether it succeeded, it can use
> > NatFeats to output results with minimal impact.
> > Here's example assembly and C-code for AHCC,
> > GCC/GAS and VBCC/VASM:
> > https://git.tuxfamily.org/hatari/hatari.git/tree/tests/natfeats
> it depends on the case, most of the time interpreting the results
> means looking at the screen and checking if some pixels are aligned
> or in different colors (depending on which video test is performed),
> which is not usable with natfeats.
We could maybe create a screenshot at the end and then compare if the
result is the same as a reference picture? Or we could hexdump the
screenshot and look for some magic byte sequences there? ... sounds all
a little bit fragile, but still better than nothing, I guess.
Or we add something similar to what is now done in the QEMU regression
i.e. use Python OpenCV to hunt for the right results in the screenshots.