|Re: [hatari-devel] Re: Feature request: allow to specify "-d" with autostart|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
Le 16/06/2017 à 23:08, Eero Tamminen a écrit :
On 06/17/2017 12:08 AM, Nicolas Pomarède wrote:
Le 16/06/2017 à 22:50, Eero Tamminen a écrit :
Hm. I'm doing builds with DebugRelease (-O2), but when I switched to
Release (-O3) build type, I do get the warning too.
Anyway, it's still a bug in GCC warnings code.
(And not the first one. Earlier GCC showed a *lot* of bogus warnings
because warnings checks were done before most of the optimization
passes which actually analyze whether given situation can actually
I agree, but since people compiling Hatari (individual or distrib
maintainers) are more likely to compile in "release" mode, I think we
should remove as much warnings as possible, even if that's due to a lack
of "cleverness" from the compiler.
thanks, confirmed when compiling
Maybe ask Toni to fix them and/or send him a patch?
I did for most of them ; but the remaining ones are often related to
float of 64 bit operations, which could require cast and sometimes have
unwanted side effects depending on the compiler. And since Windows is
the main target for winuae, it takes precedence in code changes :)