From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor
Date: Wed, 19 Sep 2018 17:54:26 -0400 [thread overview]
Message-ID: <f4051fbd-eb54-023a-8f44-ce21d1ef785c@users.sourceforge.net> (raw)
In-Reply-To: <CA+t6X7cWMK2-Jk+VuD0PaivaZZSRS+404AyJ6jWJqjRu2u8+=A@mail.gmail.com>
On 9/19/18 5:45 PM, gevisz wrote:
> вт, 18 сент. 2018 г. в 22:44, George Kettleborough <kettleg@gmail.com>:
>> If you can run gcc on the new system first you can find out what flags
>> -march=native would produce and use those. See:
>> https://blogs.gentoo.org/mgorny/2014/06/23/inlining-marchnative-for-distcc/
> Thank you for the link.
>
> It would be useful if I had an access to the target computer and decided
> to set up distcc. May be I would. In the future. However, currently, I don't
> have access to the target computer and hope to get without such an access.
> Just with the full name of the processor and the output of lspci command
> run on the target computer, which I got only a few minutes ago.
> The corresponding image is attached to this e-mail.
>> On Tue, 18 Sep 2018 at 08:24, gevisz <gevisz@gmail.com> wrote:
>>> Currently, I am prepairing to build Gentoo system on
>>> computer with AMD Athlon 64 X2 for computer with
>>> Intel Pentium Dual-Core E2160 SLA8Z Malay processor.
>>>
>>> What will be the correct march cflag for Intel Pentium
>>> Dual-Core E2160 SLA8Z Malay processor to set up in
>>> make.conf ?
>>>
>>> Am I right to use amd64 stage3 for Intel Pentium
>>> Dual-Core E2160 SLA8Z Malay processor?
>>>
>>> Thank you in advance.
Unless I'm missing something, I'm surprised nobody has mentioned one
potential problem. Unless you are careful, code you compile for an AMD
may not run on an Intel. If you are just going to compile binary
packages to move and install, this might be OK (assuming you don't trip
over trying to run test during a build.) You should be able to come up
with settings so compiled code will run on either architecture, but I
have no idea what the side effects might be, such as larger and/or less
efficient code. I almost wonder if this doesn't count as
cross-compiling, even though it is not a totally incompatible
architecture. Hopefully someone can either expand on this, or tell me
why I'm barking up the wrong tree.
Jack
next prev parent reply other threads:[~2018-09-19 21:56 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 [this message]
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
[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=f4051fbd-eb54-023a-8f44-ce21d1ef785c@users.sourceforge.net \
--to=ostroffjh@users.sourceforge.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