no one is working on long double support for non-x86 and having this test
fail all the time can mask the introduction of other (more important)
cdecl bugs
git-svn-id: trunk@8393 -
The downside is that because it is context-insensitive, several
(correct) optimizations which were performed in the past no longer
are now (and while some new ones are done now, the downside is bigger
-- but at least the code should be correct in all cases now)
git-svn-id: trunk@8385 -
are probably no longer correct when running in a window on a higher
resolutions, because everything's now 4:3 I guess) (mantis #5190)
* fixed aspect ratio logic for circle/ellipse (only circle gets adjusted)
(mantis #5190)
* clear window to black when initing graphics mode on Mac OS X
git-svn-id: trunk@8373 -
TOption.TargetDefines and call it before parsing the config file,
so extra defines like UNIX and WINDOWS are already defined while
parsing the config file (mantis #9450)
git-svn-id: trunk@8371 -
- Enables support for resource types;
- Enables support for numeric resource IDs;
- Removes initialization and runtime resource info. That initialization only did two pointer additions per resource, but required use of ansistrings and memory manager. I believe that positive impact on resource usage overweights performance impact from inlining the pointer additions...
git-svn-id: trunk@8368 -
perform the transformation of x:=f(hiddencomplexresult, ..)
-> f(x, ...) (the compiler now performs some very
conservative escape analysis for such types)
git-svn-id: trunk@8361 -
transformation, so getpixel works even better (hopefully 100% now)
* fixed usage of lineclipped when using native line drawing functions
* window was one pixel less tall than the intended resolution,
and clearviewport did not clear the entire offscreen buffer
- commented out some debugging code
git-svn-id: trunk@8353 -
constants. The default is currently 32 bits/single, which corresponds
to the old behaviour (constants which cannot be exactly represented
in the default/chosen precision will also still be automatically
upgraded to higher precision). Supported constructs:
* Command line switch -CF<x>
* Compiler directive {$MINFPCONSTPREC <x>}
whereby in both cases <x> can be default, 32 or 64. 80 is not supported
because there is no generic way to figure out whether the current target
actually supports 80 bit precision floating point calculations while
parsing the command line switches (pbestreal can still change in case of
win64 or -Cfsse2)
git-svn-id: trunk@8349 -
