On Tue, Oct 04, 2011 at 12:41:46AM -0300, Paulo César Pereira de Andrade wrote:
2011/10/3 Steve McIntyre steve.mcintyre@linaro.org:
I think I am in the "free software zealot" position here :-)
That's fair enough. :-)
So, a few minutes ago I was pointed to http://wiki.meego.com/Hardware-accelerated_graphics_on_Pandaboard_using_MeeG... that points to http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0041c/Babdhhd...
or for some related information http://groups.google.com/group/pandaboard/browse_thread/thread/cd69411c1cb60...
For now I have been only considering gcc as compiler, and the link in infocenter.arm.com appears to suggest that the mapping, to have an armv7 distro capable of running existing armv5 or older software, would be:
gcc -mfloat-abi=softfp -mfpu=vfpv3-d16 -> tcc /hardfp /nofpregargs
possibly replacing vfpv3-d16 with neon
but the problem is, the tcc (arm C compiler!?) calls softfp what gcc calls -mfloat-abi=soft, but "now" only supports hardp with what gcc calls -mfloat-abi=hard calling convention.
*Warning*: You should be aware that this infocenter document is *withdrawn* and should not be relied upon! It's ancient and misleading and not relevant to current ABI discussions.
/fpregargs Floating-point arguments are passed in floating-point registers. This option is not available for in tcc or tcpp, and is the default for ARM if /hardfp is selected. /nofpregargs Floating-point arguments are not passed in floating-point registers. This option is not available in tcc or tcpp. This option is obsolete and is available for backwards compatibility only.
Note, that "tcc" issues is news to me, as so far I was only considering gcc and its optimizations that make breaking the abi pretty much nonsense, but was not considering an extra compiler, that may be being used to build external, non open source libraries, e.g. libGLes*.
Don't worry about it, it's not an issue at all. Modern tools will work just fine.
Cheers,