>From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] > >There's a rough early version available on >http://wiki.meego.com/Quality/Compliance > >We'd like to ask for feeback on this at various levels, >the most important being the highest level: does it >get anywhere close to describing an implementation of >the basic principles, as presented most recently >at the TSC meeting:
I think there should something stated about the instruction set and compiler targets used, at least on ARM side. Simply stating ARMv7 is not enough as the architecture leaves too much as optional (like VFP, NEON) and details like instruction timings etc may differ greatly between different implementations of the architecture. Also architecture licensees of the ARMv7 may more or less implement whatever they feel like on top of the architecture. Sure you can build compliant binaries using only ARMv7 but they will not be optimal at all in real life. This opens up a whole can of worms for binary compatibility but if you strictly follow ARMv7 then you could not use e.g. NEON unit at all. And with e.g OMAP3 based chips you just cannot make a product (or many 3rd party apps like games) without it. At minimum you should be able to build you packages with different gcc-targets, so that there can be difference in binaries for -march=armv7-a, -mcpu=cortex-a8 and -mpcu=cortex-a9,... etc. tatu _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
