From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: fortran@gcc.gnu.org
Subject: replacing hardware?
Date: Thu, 13 Apr 2023 09:43:26 -0700 [thread overview]
Message-ID: <ZDgxLg9CtJQ1m3FK@troutmask.apl.washington.edu> (raw)
All,
The systems that I've used while hacking on gfortran
bugs and features are starting to show their age. I'm
in the early stage of put together the wishlist for
a budget friendly replacement. While I'll likely go
with a Ryzen7 cpu, NVME M2 drives, and as much memory
as I can afford, I'm looking for recommendations for
a budget friendly video/gpu card that will allow me to
take a deeper dive into openacc/openmp and offloading.
Anyone have a suggestion?
Note, I've mostly used FreeBSD over the last 25+ years.
I suspect that pursuing offloading may be easier with
a flavor linux. Any recommendation would also be
appreciated.
--
Steve
next reply other threads:[~2023-04-13 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 16:43 Steve Kargl [this message]
2023-04-14 6:40 ` Richard Biener
2023-04-14 11:01 ` o1bigtenor
2023-04-15 1:37 ` Jerry D
[not found] <mailman.2280.1681460310.1979823.fortran@gcc.gnu.org>
2023-04-14 12:44 ` Roland Hughes
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=ZDgxLg9CtJQ1m3FK@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).