From: gevisz <gevisz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor
Date: Wed, 3 Oct 2018 14:03:06 +0300 [thread overview]
Message-ID: <CA+t6X7fTf1oTxBCj0zQkvRTJ0mxBozjzN_tfPyD4ur9LKweAbw@mail.gmail.com> (raw)
In-Reply-To: <20181003094951.GA2572@waltdnes.org>
ср, 3 окт. 2018 г. в 12:50, Walter Dnes <waltdnes@waltdnes.org>:
>
> What's happening is that the ebuild is going through a lookup table of
> CPU flags, and saying... "if you invoke a certain advanced feature, then
> you also have to invoke the base version of that feature". If you ask
> for the advanced feature, but not the base feature, it's like trying to
> build the top 4 storeys of a 10-storey building without the bottom 6
> storeys. From your output...
>
> If you're calling for avx2, then you also need avx
> > cpu_flags_x86_avx2? ( cpu_flags_x86_avx )
>
> If you're calling for sse4_2, then you also need sse4_1
> > cpu_flags_x86_sse4_2? ( cpu_flags_x86_sse4_1 )
>
> If you're calling for sse4_1, then you also need ssse3
> > cpu_flags_x86_sse4_1? ( cpu_flags_x86_ssse3 )
>
> If you're calling for ssse3, then you also need sse3 (count the "s")
> > cpu_flags_x86_ssse3? ( cpu_flags_x86_sse3 )
>
> If you're calling for sse3, then you also need sse2
> > cpu_flags_x86_sse3? ( cpu_flags_x86_sse2 )
>
> If you're calling for sse2, then you also need sse
> > cpu_flags_x86_sse2? ( cpu_flags_x86_sse )
>
> If you're calling for sse, then you also need mmxext
> > cpu_flags_x86_sse? ( cpu_flags_x86_mmxext )
>
> If you're calling for mmxext, then you also need mmx
> > cpu_flags_x86_mmxext? ( cpu_flags_x86_mmx )
>
> AMD If you're calling for 3dnowext, then you also need 3dnow
> > cpu_flags_x86_3dnowext? ( cpu_flags_x86_3dnow )
>
> AMD If you're calling for 3dnow, then you also need mmx
> > cpu_flags_x86_3dnow? ( cpu_flags_x86_mmx )
>
> Basically, if flag B is an extension of flag A and builds on it, then
> calling flag B requires calling flag A. Think of it as a "march flag
> dependency tree".
Ok, thank you for explanation.
Interestingly, I have build almost entire system without
mmxext flag and only firefox, ffmpeg and vlc started
to complane about it.
next prev parent reply other threads:[~2018-10-03 11:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 7:22 [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor gevisz
2018-09-18 19:44 ` George Kettleborough
2018-09-19 21:45 ` gevisz
2018-09-19 21:54 ` Jack
2018-09-19 22:08 ` gevisz
2018-09-20 0:33 ` Andrew Udvare
2018-09-18 21:52 ` james
2018-09-19 21:52 ` gevisz
2018-09-19 8:37 ` Walter Dnes
2018-09-19 22:00 ` gevisz
2018-09-23 7:09 ` Walter Dnes
2018-09-24 15:49 ` james
2018-09-25 4:07 ` gevisz
2018-09-25 4:10 ` gevisz
2018-09-25 8:11 ` gevisz
2018-09-28 4:04 ` Walter Dnes
2018-09-28 9:33 ` Marc Joliet
2018-10-03 4:36 ` Mike Gilbert
2018-10-02 19:45 ` gevisz
2018-10-02 20:18 ` gevisz
2018-10-03 9:49 ` Walter Dnes
2018-10-03 11:03 ` gevisz [this message]
[not found] <wziCm-7RE-3@gated-at.bofh.it>
[not found] ` <wzGbE-4TG-5@gated-at.bofh.it>
[not found] ` <wzSPv-407-1@gated-at.bofh.it>
[not found] ` <wB6Qp-6uG-1@gated-at.bofh.it>
2018-09-24 15:30 ` james
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+t6X7fTf1oTxBCj0zQkvRTJ0mxBozjzN_tfPyD4ur9LKweAbw@mail.gmail.com \
--to=gevisz@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox