From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out2.suse.de (smtp-out2.suse.de [IPv6:2a07:de40:b251:101:10:150:64:2]) by sourceware.org (Postfix) with ESMTPS id BB1C83858C53 for ; Fri, 26 Jan 2024 12:41:56 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org BB1C83858C53 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=suse.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=suse.de ARC-Filter: OpenARC Filter v1.0.0 sourceware.org BB1C83858C53 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2a07:de40:b251:101:10:150:64:2 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1706272918; cv=none; b=cL+Qn38Fzsw9vfLJHBQ6W6FzHlXxS/HOShi2KVRAMesvrrlsDP/WjfFGCe86/u0OHIHzzHq6vcd0acKENcVS5pc48XQENaeesyylKzXQab17mdZXpQWuYelxcb19rhC5VkYd+tweeOsAoZd3r0rgP3kY3Cv0rzUCqe52jy0Ma0Y= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1706272918; c=relaxed/simple; bh=oS0p2IR4t9G++drA+drHeJkvqSVnzj6ufPeKvKPtMC4=; h=DKIM-Signature:DKIM-Signature:DKIM-Signature:DKIM-Signature:Date: From:To:Subject:Message-ID:MIME-Version; b=qg6qYG6fUVBdoRmcSvADKRqBuc6zY3dzT+BVXO2lL/o7wm89ifLljmD+w2mviZPHKNebyqne+UTZ0hgtccjHz3ssI0jxuu3L9qUBbV3RmmtocjSiqCX25eFMmZEOTkmmR7TXCqNRXb+FcpVJk4mZLM9SeTXP5M+22W/4cN08i50= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from [10.168.4.150] (unknown [10.168.4.150]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id BAEC21FB92; Fri, 26 Jan 2024 12:41:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1706272915; h=from:from:reply-to: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=hkbk3W7CUM7MumZ9tge7TR9SgihMIXejUCCq27+/Ffw=; b=s/eXuDYpTMlHCWoNEu5BhvOYIT+GghAFG0z3Y4F97N6zogGsRA0bFEfD+Xnmc2P6btGft+ iyfpY6If2FcSfowUUz4KlPS1B6F3X9bgcJxtMRcB+f0WmoYeWr7YT3Fm02jqHgDYQfiu4a fNOxbQFovvmk8j2DGYAOEqfzd6QSCFo= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1706272915; h=from:from:reply-to: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=hkbk3W7CUM7MumZ9tge7TR9SgihMIXejUCCq27+/Ffw=; b=tvEw/6obyYcEjR/qQ2/gFBHMJNRo6g4Wsgh/iyDeCQWOZwUpb5ER1F/78DGWaY9zhpwbUJ L6iRqWCu77xUwbCg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1706272915; h=from:from:reply-to: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=hkbk3W7CUM7MumZ9tge7TR9SgihMIXejUCCq27+/Ffw=; b=s/eXuDYpTMlHCWoNEu5BhvOYIT+GghAFG0z3Y4F97N6zogGsRA0bFEfD+Xnmc2P6btGft+ iyfpY6If2FcSfowUUz4KlPS1B6F3X9bgcJxtMRcB+f0WmoYeWr7YT3Fm02jqHgDYQfiu4a fNOxbQFovvmk8j2DGYAOEqfzd6QSCFo= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1706272915; h=from:from:reply-to: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=hkbk3W7CUM7MumZ9tge7TR9SgihMIXejUCCq27+/Ffw=; b=tvEw/6obyYcEjR/qQ2/gFBHMJNRo6g4Wsgh/iyDeCQWOZwUpb5ER1F/78DGWaY9zhpwbUJ L6iRqWCu77xUwbCg== Date: Fri, 26 Jan 2024 13:40:47 +0100 (CET) From: Richard Biener To: Tobias Burnus cc: Andrew Stubbs , gcc-patches@gcc.gnu.org Subject: Re: [patch] amdgcn: config.gcc - enable gfx1030 and gfx1100 multilib; add them to the docs In-Reply-To: Message-ID: <9q0o3r09-2584-9534-6684-s73r0o896359@fhfr.qr> References: <20240124124304.1780645-1-ams@baylibre.com> <14019d71-7ffb-40e6-892f-5d8168242614@baylibre.com> <2ea86540-c32a-4869-943a-ba1f1aaace03@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Authentication-Results: smtp-out2.suse.de; none X-Spamd-Result: default: False [-0.26 / 50.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DKIM_SIGNED(0.00)[suse.de:s=susede2_rsa,suse.de:s=susede2_ed25519]; FUZZY_BLOCKED(0.00)[rspamd.com]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; BAYES_HAM(-0.16)[69.45%] X-Spam-Level: X-Spam-Score: -0.26 X-Spam-Status: No, score=-5.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE 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 Fri, 26 Jan 2024, Tobias Burnus wrote: > Now with patch ... > > Tobias Burnus wrote: > > Hi all, hi Richard & Andrew, > > > > Am 24.01.24 um 17:01 schrieb Tobias Burnus: > >> This patch obviously depends on Andrew's; he wrote in the previous email of > >> this thread regarding his patch: > >> > >> Andrew Stubbs wrote: > >>> This is enough to get gfx1100 working for most purposes, on top of the > >>> patch that Tobias committed a week or so ago; there are still some test > >>> failures to investigate, and probably some tuning to do. > >>> > >>> It might also get gfx1030 working too. @Richi, could you test it, > >>> please? > > > > If gfx1030 doesn't work, I would propose my patch previously in the thread, > > https://gcc.gnu.org/pipermail/gcc-patches/2024-January/643835.html > > > > This patch assumes that both gfx1100 and gfx1030 are now working: > > > >> Okay to enable gfx1100 multilib building and to document gfx1100 in the > >> manual? > > and, with this patch, additionally gfx1030? > > > > OK for mainline, once Andrew's patch is in? > Tobias Looks good to me. +@item gfx1030 +Compile for RDNA2 gfx1030 devices (GFX10 series). + +@item gfx1100 +Compile for RDNA3 gfx1100 devices (GFX11 series). Btw, "GFX10" series isn't precise as it's only the high-end parts that are covered by gfx1030, there's gfx103[0-6] where hopefully at least gfx1031, gfx1032 and gfx1034 (the dGPU variants) are trivial to support as well(?). Using gfx103x might be better that way, OTOH if APU vs dGPU will make a compilation target difference then gfx103d vs gfx103a maybe? "GFX10" series might be also not know to users, but I'm unsure we can list AMD product names here? Richard.