From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 0916F139083 for ; Sun, 3 Dec 2017 07:23:24 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 193DAE0F65; Sun, 3 Dec 2017 07:23:16 +0000 (UTC) Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 792E6E0F3B for ; Sun, 3 Dec 2017 07:23:15 +0000 (UTC) Received: by mail-lf0-x236.google.com with SMTP id e137so15857237lfg.5 for ; Sat, 02 Dec 2017 23:23:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mclure-org.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=/rXdoc32h+N1o7FtlNb4IAGwPIEt9dGsECR1w7ThjPA=; b=NE8GuVrkxDcrjdNh0tEwIIsG9rJjrSYiLGGVW2MwYlkv6eC+ZyZYXxyzkNYmYGOXAa WDGXRfjE8LTz7Kao8Qt/+RBibT77Vmkid2T35mA86jW63XpVlUynyTmbVQ+pEjo0Jt/1 OF8y18iZNmBc0cKNwerfJ3jK9aDUWbRN3rPlkx5KzAFZPVIV2XZ1tbGu5YhXliw1NbHn 8cA8fniRvhJ6yUdWGA+EZ5A+yVvkY442YhLIJqowPpb1jCvZOq4mjCmB6nP/U3+yPK9e DqAut4VoJrf4ihWIa2Fg8o1cLwZqnglMI3g929BOW2iL24458CfbD5CWbqRiJsJ/2wkX grRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/rXdoc32h+N1o7FtlNb4IAGwPIEt9dGsECR1w7ThjPA=; b=cquV5N1x38+BAd1qJU36Ctk04fvKs4a7tJ98tG+uypn8L2BLt5O10hn6LM1nMyTOvp 4KQ3n8bgjBnf/C6BKo+wx3QrgEsOD//wq9jQlWU7muNMPj3oUCcGlMGw3e50cDFDkepQ GrrbQa5t+GqRg6/rCLdnGink6Nq4VICv2EUzPmJtQDtLZpV2mUAYfg4AcmBJbU+aFNyH Ls3aIeYVrxdTP36Gyfk6z8McubBlQW4glaoc8isi7sD6yFwyes3PJFLENMDgXvieEu+n M5C+Kbg6VMt+XERIquzly1NHZXdCRQHHqzyEdtqWOVXY9Yh/en1Rv++svlLqR26/Fhra 8zWA== X-Gm-Message-State: AJaThX5CSvMVD0fj8Vc0Tbbz62VtZVeSP53GSrxzpYSSy5HVwPQ7Yamn Pm1kOSNyE3544YTJAUqBR1brS2c= X-Google-Smtp-Source: AGs4zMYhHjsnbk7QdNnBnqzH5NQcsaAP5abI8sfBMVWF2fhbrUbvYjqabkGUk/neLmCbMgs+J9zRig== X-Received: by 10.46.0.218 with SMTP id e87mr7746735lji.65.1512285792940; Sat, 02 Dec 2017 23:23:12 -0800 (PST) Received: from mail-lf0-f54.google.com (mail-lf0-f54.google.com. [209.85.215.54]) by smtp.gmail.com with ESMTPSA id c1sm2125189ljb.78.2017.12.02.23.23.11 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 02 Dec 2017 23:23:12 -0800 (PST) Received: by mail-lf0-f54.google.com with SMTP id r143so15799042lfe.13 for ; Sat, 02 Dec 2017 23:23:11 -0800 (PST) X-Received: by 10.25.198.147 with SMTP id w141mr5470552lff.84.1512285791575; Sat, 02 Dec 2017 23:23:11 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.25.78.28 with HTTP; Sat, 2 Dec 2017 23:23:10 -0800 (PST) From: Manuel McLure Date: Sat, 2 Dec 2017 23:23:10 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: [gentoo-user] CFLAGS for both AMD64 and Intel? To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary="94eb2c1a06c667e749055f6a79e7" X-Archives-Salt: 262f7e13-5efe-4734-a9ab-3c396123b749 X-Archives-Hash: adb675e2de192feaf097fcc845117196 --94eb2c1a06c667e749055f6a79e7 Content-Type: text/plain; charset="UTF-8" Here's the situation. I have a system that's been running for many years with an Athlon 5050e processor. The system is built with CFLAGS="-march=k8-sse3 -O2 -pipe -msse3" CPU_FLAGS_X86="3dnow 3dnowext mmx mmxext sse sse2 sse3" I have the possibility of upgrading the system to a first-generation Intel Core i5 which should give a nice speed boost, but of course the Intel chip doesn't understand 3dnow or 3dnowext, so I'll have to do a system rebuild before I switch out the motherboard/processor. It seems pretty obvious that I have to take "3dnow 3dnowext" out of CPU_FLAGS_X86, but what CFLAGS would be recommended for a system that will still run with the AMD processor but won't fall over when I switch to the Intel processor? Once I have the Intel in place I can rebuild with options more suited for that chip, but I want to make sure I don't end up in a catch-22 situation. -- Manuel A. McLure WW1FA ...for in Ulthar, according to an ancient and significant law, no man may kill a cat. -- H.P. Lovecraft --94eb2c1a06c667e749055f6a79e7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Here's the situation. I have a system that's been = running for many years with an Athlon 5050e processor. The system is built = with

CFLAGS=3D"-march=3Dk8-sse3 -O2 -pipe -msse3&qu= ot;
CPU_FLAGS_X86=3D"3dnow 3dnowext mmx mmxext sse sse2 sse3"<= /div>

I have the possibility of upgrading the system to a firs= t-generation Intel Core i5 which should give a nice speed boost, but of cou= rse the Intel chip doesn't understand 3dnow or 3dnowext, so I'll ha= ve to do a system rebuild before I switch out the motherboard/processor. It= seems pretty obvious that I have to take "3dnow 3dnowext" out of= CPU_FLAGS_X86, but what CFLAGS would be recommended for a system that will= still run with the AMD processor but won't fall over when I switch to = the Intel processor? Once I have the Intel in place I can rebuild with opti= ons more suited for that chip, but I want to make sure I don't end up i= n a catch-22 situation.

--
Manuel A. M= cLure WW1FA <manu= el@mclure.org> <http://www.mclure.org>
...for in Ulthar, according to an ancie= nt and significant law,
no man may kill a cat.=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 -- H.P. Lovecraf= t
--94eb2c1a06c667e749055f6a79e7--