public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Guilherme Amadio <amadio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [RFC] Make 'cuda' a global USE flag
Date: Mon, 17 Sep 2018 16:00:26 +0200	[thread overview]
Message-ID: <20180917135849.GA28786@gentoo.org> (raw)

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


             reply	other threads:[~2018-09-17 14:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17 14:00 Guilherme Amadio [this message]
2018-09-17 17:58 ` [gentoo-dev] [RFC] Make 'cuda' a global USE flag Jason Zaman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180917135849.GA28786@gentoo.org \
    --to=amadio@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox