public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Benson Muite <benson_muite@emailplus.org>
Cc: Richard Biener <richard.guenther@gmail.com>, fortran@gcc.gnu.org
Subject: Re: GPU offloading question
Date: Sat, 3 Feb 2024 10:37:52 -0800	[thread overview]
Message-ID: <Zb6IAE69HrRTdGBt@troutmask.apl.washington.edu> (raw)
In-Reply-To: <cc56324b-77ee-1eb8-87a6-222c9f786674@emailplus.org>

On Sat, Feb 03, 2024 at 09:15:21PM +0300, Benson Muite wrote:
> >>>

I wrote:

> >>> Suppose one is working in a funding-constrained environment
> >>> such as an academician with limited grant funding.  If one
> >>> wanted to dabble in GPU offloading with gcc/gfortran, what
> >>> recommendations would one have for minimum required hardware?
> >>> In addition, are there any vendor software layers that are
> >>> required (such as AMD ROCm with an AMD GPU)?
> >>
> > 
> Consider https://allocations.access-ci.org/resources
> for a PI based in the USA. Use the limited funding to support your time
> improving off loading support for GFortran.


Thanks for the link.  I'll see what might be available to me.

I already support gfortran development (although not offloading)
with my limited time.  See gcc/fortran/ChangeLog* from the last
25 or so years. :-)

-- 
Steve

  reply	other threads:[~2024-02-03 18:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-03  0:21 Steve Kargl
2024-02-03 13:37 ` Richard Biener
2024-02-03 16:13   ` Steve Kargl
2024-02-03 18:15     ` Benson Muite
2024-02-03 18:37       ` Steve Kargl [this message]
2024-02-03 19:38       ` Richard Biener

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=Zb6IAE69HrRTdGBt@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=benson_muite@emailplus.org \
    --cc=fortran@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).