[gentoo-user] Flash and cpu_flags_x86_sse2

[gentoo-user] Flash and cpu_flags_x86_sse2

[ddjones]

Getting the following on updating world:

!!! The ebuild selected to satisfy "www-plugins/adobe-flash" has unmet 
requirements.
- www-plugins/adobe-flash-11.2.202.440::gentoo USE="kde -debug (-selinux)" 
CPU_FLAGS_X86="-sse2"

  The following REQUIRED_USE flag constraints are unsatisfied:
    cpu_flags_x86_sse2

  The above constraints are a subset of the following complete expression:
    cpu_flags_x86_sse2 debug? ( abi_x86_32 ) any-of ( abi_x86_64 abi_x86_32 )



Use flag sse2 is set, verified by both euse and a manual examination of 
make.conf.  What am I missing?

-- 
"each generation wastes a little more of the future with greed and lust for 
riches" - archie the cockroach [Don Marquis]

Re: [gentoo-user] Flash and cpu_flags_x86_sse2

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 503 bytes --]

On Thu, 29 Jan 2015 19:46:57 -0500, ddjones wrote:

>   The above constraints are a subset of the following complete
> expression: cpu_flags_x86_sse2 debug? ( abi_x86_32 ) any-of
> ( abi_x86_64 abi_x86_32 )
> 
> 
> 
> Use flag sse2 is set, verified by both euse and a manual examination of 
> make.conf.  What am I missing?

CPU specific USE flags have moved, there was a news item about it

eselect news read


-- 
Neil Bothwick

A man needs a mistress - just to break the monogamy

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] Flash and cpu_flags_x86_sse2

[Gevisz]

On Thu, 29 Jan 2015 19:46:57 -0500 ddjones <ddjones@riddlemaster.org> wrote:

> Getting the following on updating world:
> 
> !!! The ebuild selected to satisfy "www-plugins/adobe-flash" has unmet 
> requirements.
> - www-plugins/adobe-flash-11.2.202.440::gentoo USE="kde -debug (-selinux)" 
> CPU_FLAGS_X86="-sse2"
> 
>   The following REQUIRED_USE flag constraints are unsatisfied:
>     cpu_flags_x86_sse2
> 
>   The above constraints are a subset of the following complete expression:
>     cpu_flags_x86_sse2 debug? ( abi_x86_32 ) any-of ( abi_x86_64 abi_x86_32 )
> 
> 
> 
> Use flag sse2 is set, verified by both euse and a manual examination of 
> make.conf.  What am I missing?

eselect news list

[gentoo-user] Re: Flash and cpu_flags_x86_sse2

[James]

Neil Bothwick <neil <at> digimed.co.uk> writes:



> CPU specific USE flags have moved, there was a news item about it
> eselect news read
 
yea, ok.

so I ran the script and got:

# cpuinfo2cpuflags-x86
CPU_FLAGS_X86="aes avx fma3 fma4 mmx mmxext popcnt sse sse2 sse3 sse4_1
sse4_2 sse4a ssse3 xop"

But, looking at : /usr/portage/profiles/desc/cpu_flags_x86.desc
I surmise:

CPU_FLAGS_X86="mmx sse sse2 sse3 ssse3 sse4 sse4_1 sse4_2 sse4a ssse3 \
mmx mmxext xop 3dnowprefetch  3dnow 3dnowext aes avx  avx2 fma3 fma4 \
padlock popcnt "


Some discussion would be keen, as I'd just assume if any ebuild called
a specific instruction set feature, then it should be listed globally
for that processor. In fact, I'll bet there are actually few packages
that need any of those (amd64)CPU flags turned off; so why not just
list all amd64 CPU flags by default and have the user use a -feature,
flag setting, per package? 

After all, if a software dev goes to the trouble to
research how to make their software run (faster), via specific instruction
sets of a given processor, it's a pretty good bet that those ought to be 
invoked. Ok of coarse I have no idea if GCC(++) is doing anything
"squirrely" in the compilers lately.... (related to CPU flag settings);
mostly because that is some voluminous research and reading.

What would be cool, is if the devs took the entire list of cpu flags
from proc/cpuinfo and piped it thru a simple validation script (equery
hasuse) to generate the maximum flags to set by default for a given cpu. I
see no reason this should be limited to either x86 or amd64. Arm64 is out
in the wild and it will not be too much longer before this list has
numerous questions about arm64 processor flags settings, for the myriad
of arm64 processors headed to the linux distros.


James

[1] http://thread.gmane.org/gmane.linux.gentoo.user/165425/focus=165441

Re: [gentoo-user] Re: Flash and cpu_flags_x86_sse2

[Mike Gilbert]

On Mon, Feb 2, 2015 at 4:43 PM, James <wireless@tampabay.rr.com> wrote:
> But, looking at : /usr/portage/profiles/desc/cpu_flags_x86.desc
> I surmise:
>
> CPU_FLAGS_X86="mmx sse sse2 sse3 ssse3 sse4 sse4_1 sse4_2 sse4a ssse3 \
> mmx mmxext xop 3dnowprefetch  3dnow 3dnowext aes avx  avx2 fma3 fma4 \
> padlock popcnt "
>

Exactly how did you "surmise" your list?

> What would be cool, is if the devs took the entire list of cpu flags
> from proc/cpuinfo and piped it thru a simple validation script (equery
> hasuse) to generate the maximum flags to set by default for a given cpu.

That's exactly what cpuinfo2cpuflags-x86 does.

[gentoo-user] Re: Flash and cpu_flags_x86_sse2

[James]

Mike Gilbert <floppym <at> gentoo.org> writes:


> > CPU_FLAGS_X86="mmx sse sse2 sse3 ssse3 sse4 sse4_1 sse4_2 sse4a ssse3 \
> > mmx mmxext xop 3dnowprefetch  3dnow 3dnowext aes avx  avx2 fma3 fma4 \
> > padlock popcnt "

> Exactly how did you "surmise" your list?

cat /usr/portage/profiles/desc/cpu_flags_x86.desc

which is a subset of the CPU flags found in /proc/cpuinfo


> > What would be cool, is if the devs took the entire list of cpu flags
> > from proc/cpuinfo and piped it thru a simple validation script (equery
> > hasuse) to generate the maximum flags to set by default for a given cpu.
> That's exactly what cpuinfo2cpuflags-x86 does.

So the list given by the current script does not include all of the
flags listed in //usr/portage/profiles/desc/cpu_flags_x86.desc


That's the explanation I was looking for. The only thing I can think
of is the extra flags are not every used in current packages found
in the portage tree. I wonder if gcc(++) might could make use
of those flags. I'm not making a statement, but framing a question.

But I would think that is the reason for the subset of /proc/cpuinfo
that forms the flags listed in :
/usr/portage/profiles/desc/cpu_flags_x86.desc

hth,
James