On 9/19/18 5:45 PM, gevisz wrote:
вт, 18 сент. 2018 г. в 22:44, George Kettleborough <kett...@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 <gev...@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
