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 995E1138334 for ; Mon, 17 Sep 2018 14:00:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3DF03E0977; Mon, 17 Sep 2018 14:00:35 +0000 (UTC) Received: from smtp.gentoo.org (dev.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (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 DF28BE08EB for ; Mon, 17 Sep 2018 14:00:34 +0000 (UTC) Received: from gentoo.org (unknown [IPv6:2001:1458:202:96::101:7295]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: amadio) by smtp.gentoo.org (Postfix) with ESMTPSA id 82078335CDA for ; Mon, 17 Sep 2018 14:00:31 +0000 (UTC) Date: Mon, 17 Sep 2018 16:00:26 +0200 From: Guilherme Amadio To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] [RFC] Make 'cuda' a global USE flag Message-ID: <20180917135849.GA28786@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.10.1 (2018-07-13) X-Archives-Salt: f54503dd-99c3-4caf-b44d-b6e2633d4c22 X-Archives-Hash: 672bb7b7b1817663643f510e23fd9f28 Hi everyone, We have several packages (~35) with local USE=cuda. Should we make that a global USE flag? It's a quite generic flag for GPU support, so I was surprised to learn it was still local when I added support for it to a package recently. Another thing we might want to discuss is a global setting for the CUDA architecture to be used¹. We compile from source, so it would be a shame not to compile with the right features for newer GPUs². Maybe just advertising the NVCCFLAGS one should put in make.conf is enough? Cheers, —Guilherme 1. https://docs.nvidia.com/cuda/cuda-compiler-driver-nvcc/index.html#options-for-steering-gpu-code-generation 2. https://docs.nvidia.com/cuda/cuda-compiler-driver-nvcc/index.html#gpu-feature-list