wm4 74b8223da6 build: switch to -std=c99 for saner float semantics ... This fixes a weird bug with aspect ratio handling. It has to do with float handling: with -std=gnu99, gcc implicitly enables broken non- standard semantics giving float variables excess precision. This can for example make this fail in theory: "float a = 0.1; assert(a == a);" While standard C allows excess precision _within_ expressions, it requires truncation when storing float values in variables of types "float" or "double". The "gnu99" mode breaks this. It can be unbroken by using "c99", or by specifying -fexcess-precision=standard. The former seems less likely to break compilers other than modern gcc. Note that -ffloat-store would also fix this, but also makes float expressions less efficient and less precise for no reason. The code that mistakenly fails because of this is dec_video.c line 393. It caused the container aspect to be ignored in some or all situations, depending how the compiler optimizes. For example, on gcc-4.6 with -Os, the aspect is always ignored. In future, we should probably just get rid of storing aspects as floats.		2014-02-02 00:00:14 +01:00
..
__init__.py	…
compiler.py	build: switch to -std=c99 for saner float semantics	2014-02-02 00:00:14 +01:00
cpu.py	build: add flag for inline assembly	2013-12-29 17:39:18 +01:00
devices.py	…