From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Woodcroft Subject: CPU-specific builds Date: Sat, 1 Oct 2016 20:43:04 +1000 Message-ID: <5985e2f0-edd3-c40b-bb10-f84b233bb48d@uq.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49370) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bqHlJ-0002i4-95 for guix-devel@gnu.org; Sat, 01 Oct 2016 06:43:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bqHlG-0002uT-41 for guix-devel@gnu.org; Sat, 01 Oct 2016 06:43:21 -0400 Received: from mailhub2.soe.uq.edu.au ([130.102.132.209]:35089 helo=newmailhub.uq.edu.au) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bqHlF-0002ow-Gc for guix-devel@gnu.org; Sat, 01 Oct 2016 06:43:18 -0400 Received: from smtp2.soe.uq.edu.au (smtp2.soe.uq.edu.au [10.138.113.41]) by newmailhub.uq.edu.au (8.14.5/8.14.5) with ESMTP id u91Ah8Qc007181 for ; Sat, 1 Oct 2016 20:43:10 +1000 Received: from [192.168.1.105] (static.customers.nuskope.com.au [103.25.181.216] (may be forged)) (authenticated bits=0) by smtp2.soe.uq.edu.au (8.14.5/8.14.5) with ESMTP id u91Ah51T064116 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sat, 1 Oct 2016 20:43:08 +1000 List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: "guix-devel@gnu.org" Hi, Currently, we build a single set of x86_64 packages assuming SSE but not SSE2 instructions, but sometimes it would be nice to use more recent instructions like AVX. So I'm wondering if there is some way to specify a system more specific than 'X86_64'? I tried simply adding '--with-arch=haswell' as a configure argument in gcc-4.9 so that flag became the default for gcc usage and saw some performance improvements, though I did have to disable tests in gnutls. Hardcoding that configure flag is definitely less than ideal, I'm wondering if there is some better way that would enable us to share package updates and even substitutes for these systems? My initial thought is extending the triplet 'x86_64-unknown-linux-gnu' somehow, but I suspect others have better ideas? Thanks, ben.