Hi, Glen, Just my point. > The use of ssse3 throughout the x86 rpms is what I'm referring to, not the > GUI. '-mssse3' doesn't means any pkg which was compiled with this flag will definitely have ssse3 instructions. For some app, say multimedia/science computing......, it is useful (but also depends on compiler and other flags), but for others, say bash, even though with this flag, it still didn't include any ssse3 instructions. Meanwhile, It is hard to identify all ssse3-helpful apps/codes in meego system as well and it is also impossible to optimize any app with ssse3 instruction one by one. So setting it as one 'global' flag is not such un-reasonable. Against this, '-march=core2 -mtune=atom' is more sensitive than this.
> Or rather I'm asking, is it still the case that ssse3 is used throughout > entire suite of x86 rpms, as it was in Moblin. IMHO, yes. > Yes, it is what I'm referring to. If other x86 platforms want to base on > MeeGo Core, then does it make sense for the ssse3 optimization to be applied > to the underlying core os and not just the UX. It is a little unimaginable: if anyone else platform wants to base on MeeGo Core, but don't compile/optimize for itself, say at least -march, -mtune ...... -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Glen Gray Sent: Friday, June 11, 2010 4:07 PM To: Greg KH Cc: [email protected] Subject: Re: [MeeGo-dev] Compiling MeeGo - Other Platforms On 10 Jun 2010, at 21:28, Greg KH wrote: >>> Seriously, the SSSE3 instructions are there to help accelerate the 3d >>> graphics that MeeGo needs. Turning them off is a very noticable >>> difference. >> >> I can see how this makes sense for certain types of applications and >> libraries. > > Like the core GUI, right? That's the issue here. Yes, for netbooks, the core GUI and it's support libraries. It makes sense to optimize for that target platform for these applications and libraries. >> But how does this relate to packages in MeeGo Core for example. > > The core GUI is what I'm referring to. The use of ssse3 throughout the x86 rpms is what I'm referring to, not the GUI. Or rather I'm asking, is it still the case that ssse3 is used throughout entire suite of x86 rpms, as it was in Moblin. >> Given that different devices are going to have different UX stacks, >> abstracted to a certain degree from the underlying MeeGo os. > > Different devices can do what they like. That's not what you are > referring to here. Yes, it is what I'm referring to. If other x86 platforms want to base on MeeGo Core, then does it make sense for the ssse3 optimization to be applied to the underlying core os and not just the UX. > You are talking about the laptop image, which is > what you care about, and is what I am referring to. Possibly recent thread contributors such as Robert Rambo or someone else earlier in the thread. I'm enquiring on MeeGo x86 relying on ssse3 when it might not make sense for platforms other than netbook and certainly when it comes to non-gui parts. Admittedly a slight variation on the original posting. >> Does it make sense for libusb or bash or any of the core os packages >> to rely on ssse3 ? In theory a meego for olpc could be possible. Or >> meego for schools that targets old hardware (just random examples). > > Again, the laptop gui matters for SSSE3. libusb has no such need, as > you can well imagine. Indeed and thus the focus of my question. -- Glen Gray <[email protected]> _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
