From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 93C943847700 for ; Wed, 3 Apr 2024 09:28:02 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 93C943847700 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 93C943847700 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1712136485; cv=none; b=XtOzNrdFCQDDuepooBDtScJfB8VnGki86lLlBke7tQt6ZathWKhNNqm5tPpS+QbHcOUD0lyd8yVwzHtplpC+Fl1E9wdvrmPK51bKOUZ3EySCvnGZPrC7k1hpyz6bfF4paTgVWGtnILSE78h9IgeuE1WXCKytQB3dlKJE6JsI8qI= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1712136485; c=relaxed/simple; bh=g4A9LqH76KogCjTcvUizymQEjjMmjVal4ZaIs3BfSk4=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=XEGp7r01hBrZmGOn1WNuxoh3kGYpn4N5/twbul30iEjtloYGtQUO6t+kZTG5u8dhSbars35FKIQB8OHMvtILY5HuoKCi1eQyjcK+3VpbGYLcWst16A6oEshw/NIrb4stEcsaO2BcQjTgnv1/KMbCySm9I5MRKFRfiteeAt2fJvM= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1712136482; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=CbAyrJ5VBfwsmfsnHtWr0lKoBubwjJEdcQd03tfsLbo=; b=H8EtJSc1r+zIXKrtMGkr4H47a9Uv8q/pUuE2IsHts0xoNy4wT/UkOJemGg65ihNGtOiEhG pN1pbKH2ILpVLsHTusDN9nXv0otu7ZULrU2k/xlgJGOmBji/8NFp/MLCHdMKR+eQaA4p49 10qbvqNgthsHstmqugCYKjMr8yENUpM= Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-581-BwrOkveLMQiZNQSOU5hadw-1; Wed, 03 Apr 2024 05:28:00 -0400 X-MC-Unique: BwrOkveLMQiZNQSOU5hadw-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id BA1E03806702; Wed, 3 Apr 2024 09:27:59 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.45.224.14]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7F1F71121306; Wed, 3 Apr 2024 09:27:59 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.17.1/8.17.1) with ESMTPS id 4339RrUB1845511 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Wed, 3 Apr 2024 11:27:54 +0200 Received: (from jakub@localhost) by tucnak.zalov.cz (8.17.1/8.17.1/Submit) id 4339RrKN1845510; Wed, 3 Apr 2024 11:27:53 +0200 Date: Wed, 3 Apr 2024 11:27:53 +0200 From: Jakub Jelinek To: Tobias Burnus Cc: gcc-patches , Andrew Stubbs Subject: Re: [Patch] GCN: install.texi update for Newlib change and LLVM 18 release Message-ID: Reply-To: Jakub Jelinek References: MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.3 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-3.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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