On Mon, Oct 9, 2017 at 6:28 PM, Mark Hatle <mark.ha...@windriver.com> wrote: > On 10/9/17 12:11 PM, Andre McCurdy wrote: >> On Mon, Oct 9, 2017 at 10:01 AM, Paul Barker <pbar...@toganlabs.com> wrote: >>> On Mon, Oct 9, 2017 at 5:49 PM, Khem Raj <raj.k...@gmail.com> wrote: >>>> On Mon, Oct 9, 2017 at 9:16 AM, Paul Barker <pbar...@toganlabs.com> wrote: >>>>> On Mon, Oct 9, 2017 at 5:04 PM, Khem Raj <raj.k...@gmail.com> wrote: >>>>>> On Mon, Oct 9, 2017 at 6:15 AM, Paul Barker <pbar...@toganlabs.com> >>>>>> wrote: >>>>>>> >>>>>>> I'm looking at what I can use to determine if sse2 is supported for a >>>>>>> given machine/tune. >>>>>>> >>>>>>> In TUNE_FEATURES I could check for "core2" or "corei7" based on what's >>>>>>> in oe-core, but not sure this will cover tunings which might be >>>>>>> defined in other layers. >>>>>>> >>>>>>> Alternatively I could check TUNE_CCARGS for "-msse2" or later but that >>>>>>> feels dirty. >>>>>>> >>>>>>> Any suggestions on this? >>>>>>> >>>> >>>> Perhaps inverse is easier, meaning, set 387 for i586, i486 and i386 >>>> and leave the >>>> defaults as it is for other variants >>> >>> Sadly that won't cover it. We'd also need to cover Pentium variants >>> pre-Pentium4 and early AMD variants. It's SSE2 which is needed not the >>> original SSE instructions. >>> > > This is why 'TUNE_FEATURES' was introduced. If SSE2 (or something else) is > need > for proper configuration, then we should add a specific tune_feature and > update > the corresponding tunes. >
Is it too late in the cycle for rocko to start adding "sse2" to TUNE_FEATURES for relevant machine configurations and include files? If it's still ok to make this change for rocko then this might be the best path forward. -- Paul Barker Togán Labs Ltd -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
