From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tburnus@baylibre.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, Andrew Stubbs <ams@baylibre.com>
Subject: Re: [Patch] GCN: install.texi update for Newlib change and LLVM 18 release
Date: Wed, 3 Apr 2024 11:27:53 +0200 [thread overview]
Message-ID: <Zg0hGTE125S/tw0q@tucnak> (raw)
In-Reply-To: <fff28577-6c2b-472c-b55b-5e6580df4900@baylibre.com>
On Wed, Apr 03, 2024 at 11:09:19AM +0200, Tobias Burnus wrote:
> @@ -3954,8 +3956,8 @@ on the GPU.
> To enable support for GCN3 Fiji devices (gfx803), GCC has to be configured with
> @option{--with-arch=@code{fiji}} or
> @option{--with-multilib-list=@code{fiji},...}. Note that support for Fiji
> -devices has been removed in ROCm 4.0 and support in LLVM is deprecated and will
> -be removed in LLVM 18.
> +devices has been removed in ROCm 4.0 and support in LLVM is deprecated and has
> +been removed in LLVM 18.
Shouldn't we at configure time then detect the case where fiji can't be
supported and either error if it is included explicitly in multilib list, or
implicitly take it out from that list and arrange error to be emitted when
using -march=fiji/gfx803 ?
Sure, if one configures against LLVM 17 and then updates LLVM to 18, it will
still result in weird errors/LLVM ICEs, but at least in the common case when
one configures GCC 14 against LLVM 18 one won't suffer from those ICEs and
get clear diagnostics that fiji is sadly no longer supported.
Jakub
next prev parent reply other threads:[~2024-04-03 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 9:09 Tobias Burnus
2024-04-03 9:27 ` Jakub Jelinek [this message]
2024-04-03 10:33 ` Tobias Burnus
2024-04-03 11:22 ` Andrew Stubbs
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=Zg0hGTE125S/tw0q@tucnak \
--to=jakub@redhat.com \
--cc=ams@baylibre.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tburnus@baylibre.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).