<cutting my part of the discussion to avoid top-posting> 2010/10/25 <[email protected]>: > Hi, > > We have discussed about hardfp (and other) support in the toolchain team. > Current assumption is that hardfp will be used in MeeGo 1.2. But there are > still quite many other things to be agreed also - regarding different > compiler options and switches, etc. Those different options are currently > investigated and target is to get default settings for them, i.e. what > options are used and how. > > So hardfp is strongly wanted to be used in MeeGo 1.2. It means workload to > re-compile, etc. but in some point we must to do it anyway. Then use of > softfp should generate error when building with that option in MeeGo 1.2. >
Would it be possible to have that discussion on a meego.com list, like this one? This is where stakeholders and other interested parties are, so this would be a way to help balance the discussion and eventual decisions with those. For 1.2 work we need to keep the ARMv7 softfp port going to keep the development process running, while alongside working to port to hardfp. In practice hardfp is like entirely other architecture in MeeGo. Once hardfp is working and is on same quality level as ARMv7 softfp, we can talk about deprecating it. I agree that there's no way but going to hardfp, but due to the amount of people in different places (the LF OBS guys, the N900 hardware adaptation team, the distribution team, the QA team, etc.) needed to make this happen, as well as the consequence of an ABI break between 1.1 ARM and 1.2 ARM in developer perspective/SDK, we need to discuss this in public and plan it/get started ASAP. I propose we work towards setting up an agenda for an IRC meeting on the topic and before the meeting having input from various people who have done the work of porting any distro to hardfp and what challenges there are (Linaro, Harmattan toolchain work, etc). As well as any shortcuts we can take due to our use of OBS (LF OBS guys) The important thing is that we get started ASAP, in my opinion, so tendencies can be seen early on and proper communication regarding ABI break can be done early on, as well as making tools to work with hardfp (sysroots, cross compilers, etc) available for developers working on 1.2. How does that sound? BR Carsten Munk Nokia N900 hardware adaptation maintainer _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
