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: Thu, 20 Sep 2018 01:00:39 +0300 [thread overview]
Message-ID: <CA+t6X7e23Kw0Bizvp1irRsCp6xHjOKcaOGpAyf6hjCQ5LDgb7w@mail.gmail.com> (raw)
In-Reply-To: <20180919083722.GA31111@waltdnes.org>
ср, 19 сент. 2018 г. в 11:38, Walter Dnes <waltdnes@waltdnes.org>:
>
> On Tue, Sep 18, 2018 at 10:22:30AM +0300, gevisz wrote
>
> > What will be the correct march cflag for Intel Pentium
> > Dual-Core E2160 SLA8Z Malay processor to set up in
> > make.conf ?
>
> If you have gcc *ON THE TARGET MACHINE*, execute the command...
>
> gcc -c -Q -march=native --help=target | grep march=
>
> ...to find out what "-march=native" yields.
Unfortunately, currently, I don't have an access to the target
computer. Can I use the output of lspci instead of the command
above? I have just got it by e-mail and attached the corresponding
image to one of my previous replies in this thread.
> 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?
> > Am I right to use amd64 stage3 for Intel Pentium
> > Dual-Core E2160 SLA8Z Malay processor?
>
> Yes... assuming you want 64-bit mode.
Ok. Thank you for your reply.
next prev parent reply other threads:[~2018-09-19 22:02 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 [this message]
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
[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+t6X7e23Kw0Bizvp1irRsCp6xHjOKcaOGpAyf6hjCQ5LDgb7w@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