public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: james <garftd@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor
Date: Mon, 24 Sep 2018 11:30:12 -0400	[thread overview]
Message-ID: <6598e077-35d8-599d-fa06-5f69c03fec0d@verizon.net> (raw)
In-Reply-To: <wB6Qp-6uG-1@gated-at.bofh.it>

On 9/23/18 3:20 AM, Walter Dnes wrote:
> On Thu, Sep 20, 2018 at 01:00:39AM +0300, gevisz wrote
>> ????, 19 ????????. 2018 ??. ?? 11:38, Walter Dnes <waltdnes@waltdnes.org>:
> 
>>>  According to
>>> http://www.cpu-world.com/sspec/SL/SLA8Z.html it has...
>>>
>>> MMX SSE SSE2 SSE3 SSSE3
>>
>> Do you mean that it would be enough to set
>> CFLAGS="-O2 -pipe mmx sse sse2 sse3 ssse3"
>> without setting the march cflag at all?
> 
>   Yes, that would work.  Remember also to include in make.conf
> 
> CPU_FLAGS_X86="mmx mmxext sse sse2 sse3 ssse3"
> 
>   In your jpeg image, I see that the flags include mmx, sse, sse2, pni,
> and ssse3. "pni" == "Prescott New Instructions" == "SSE3".  Looking at
> https://gcc.gnu.org/onlinedocs/gcc-7.3.0/gcc/x86-Options.html#x86-Options
> I suggest "-march=core2" with CPU_FLAGS_X86 same as above.  The "core2"
> option uses MMX, SSE, SSE2, SSE3 and SSSE3 instructions, all of which
> show up in the listing on your jpeg.
> 
> https://en.wikipedia.org/wiki/SSE3
>> SSE3, Streaming SIMD Extensions 3, also known by its Intel code name
>> Prescott New Instructions (PNI), is the third iteration of the SSE
>> instruction set for the IA-32 (x86) architecture.
> 

Here is some short docs (by MG) on the subject, that are good to save
for future reference::


https://nlug.ml1.co.uk/2016/09/gentoo-portage-cpu_flags_x86-introduction-2015-01-28/5332

or in the gentoo wiki::
https://wiki.gentoo.org/wiki/CPU_FLAGS_X86

Note, some years ago, distcc was excellent as I used it daily. Like
most codes it changes/stresses over the years. So follow distcc
details closely if you intend for it's dependable results. Perhaps
someone (gentoo) is using it in a CI/CD configuration, which would
be of keen interest to many.


hth,
James


       reply	other threads:[~2018-09-24 15:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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

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=6598e077-35d8-599d-fa06-5f69c03fec0d@verizon.net \
    --to=garftd@verizon.net \
    --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