#How to build binary packages for another amd64 system but for it's specific march=native flags?

1 messages · Page 1 of 1 (latest)

junior scarab
#

Set CFLAGS to the equivalent of that machines march=native

#

Or a common denominator like aMd64-v3

stone blaze
#

Run gcc -march=native -Q --help=target to find out what "-march=native" means for your systems

stone blaze
#

okay so one of your systems is intel and the other is amd

#

so you're going to want to set march=x86-64-v3 probably

#

but note, that is the same march as the binhost uses, so you'll not gain any performance over using prebuilt binpkgs

#

maybe both cpu's are compatible with x86-64-v4, but you'd have to double check that before setting it

stone blaze
#

No, code specifically compiled for AMD will not run on Intel and vice versa

stone blaze
#

maybe this is possible with qemu, but honestly I don't think it's worth it.

#

the performance gain for compiling to native arch is kinda negated if you're going to compile everything twice for each cpu

junior scarab
#

So it's possible to have your faster PC be a binhost for the laptop with all of its flags.