all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Elsing <david.elsing@posteo.net>
To: guix-devel@gnu.org
Cc: ludo@gnu.org, rekado@elephly.net
Subject: Re: PyTorch with ROCm
Date: Sun, 11 Aug 2024 19:11:41 +0000	[thread overview]
Message-ID: <86le12vpqq.fsf@posteo.net> (raw)
In-Reply-To: <86msqoeele.fsf@posteo.net>

Hello,

I updated PyTorch to 2.4.0 [1, 2] and the ROCm packages to 6.1.2.
This time, I opted to put the ROCm packages into a separate channel [3]
only for one version, because the packages in Guix-HPC are intended for
many ROCm versions and only include versions up to 5.7.1 at the moment.

The PyTorch package with ROCm is also in a separate channel [4].

I tried making the GPU architectures a Guile parameter, but this does
not work because it is evaluated when the package is lowered.
`with-parameters` [5] from `(guix gexp)` also does not work here,
because IIUC it is only intended for `%current-system` and
`%current-target-system` as indicated in `compile-parameterized`. Is
that correct?

Replacing the procedure `%amdgpu-targets` in
`guix-rocm/packages/rocm-base.scm` [3] with `module-define!` works
however, but is of course more of a hack.

Cheers,
David

[1] https://issues.guix.gnu.org/72471
[2] https://codeberg.org/dtelsing/Guix/src/branch/pytorch
[3] https://codeberg.org/dtelsing/Guix-ROCm
[4] https://codeberg.org/dtelsing/Guix-ROCm-ML
[5] https://guix.gnu.org/manual/en/html_node/G_002dExpressions.html


      parent reply	other threads:[~2024-08-11 19:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-23 23:02 PyTorch with ROCm David Elsing
2024-03-24 15:41 ` Ricardo Wurmus
2024-03-24 18:13   ` David Elsing
2024-03-28 22:21 ` Ludovic Courtès
2024-03-31 22:21   ` David Elsing
2024-04-02 14:00     ` Ludovic Courtès
2024-04-03 22:21       ` David Elsing
2024-08-11 19:11 ` David Elsing [this message]

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=86le12vpqq.fsf@posteo.net \
    --to=david.elsing@posteo.net \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=rekado@elephly.net \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.