From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by sourceware.org (Postfix) with ESMTPS id 59A923858D28 for ; Fri, 4 Feb 2022 12:09:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 59A923858D28 Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 2A6D021118; Fri, 4 Feb 2022 12:09:30 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 150A313A96; Fri, 4 Feb 2022 12:09:30 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id XAULBHoX/WFSSwAAMHmgww (envelope-from ); Fri, 04 Feb 2022 12:09:30 +0000 Message-ID: Date: Fri, 4 Feb 2022 13:09:29 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.4.1 Subject: Re: nvptx multilib setup (was: [Bug target/104364] [12 Regression] OpenMP/nvptx regressions after "[nvptx] Add some support for .local atomics") Content-Language: en-US To: Thomas Schwinge Cc: gcc@gcc.gnu.org References: <87r18jt7uu.fsf@euler.schwinge.homeip.net> From: Tom de Vries In-Reply-To: <87r18jt7uu.fsf@euler.schwinge.homeip.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Feb 2022 12:09:33 -0000 On 2/4/22 08:21, Thomas Schwinge wrote: > Hi Tom! > > Taking this one to the mailing list; not directly related to PR104364: > > On 2022-02-03T13:35:55+0000, "vries at gcc dot gnu.org via Gcc-bugs" wrote: >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104364 > >> I've tested this using (recommended) driver 470.94 on boards: > > (As not every user will be using the recommended/latest, I too am doing > some testing also on oldish Nvidia/CUDA Driver versions.) Combinatorial > explosion is a problem, of course... > I am starting to suspect that I misinterpreted the nvidia website. When asking for a driver for a board, I get some driver, which I took to be the recommended one. But I started to notice changes in recommended version from 470.x to 510.x, which suggest the recommended one is just the latest one they've updated in the set of recommended drivers. So it seems inaccurate to talk about "the" recommended driver. Thanks for the testing, much appreciated. I'm currently testing with 390.x. >> while iterating over dimensions { -mptx=3.1 , -mptx=6.3 } x { GOMP_NVPTX_JIT=-O0, }. > > Do you use separate (nvptx-none offload target only?) builds for > different '-mptx' variants (likewise: '-misa'), or have you hacked up the > multilib configuration? Neither, I'm using --target_board=unix/foffload= for that. ('gcc/config/nvptx/t-nvptx:MULTILIB_OPTIONS' > etc., I suppose?) Should we add a few representative configurations to > be built by default? And/or, should we have a way to 'configure' per > user needs (I suppose: '--with-multilib-list=[...]', as supported for a > few other targets?)? (I see there's also a new > '--with-multilib-generator=[...]', haven't looked in detail.) No matter > which way: again, combinatorial explosion is a problem, of course... > As far as I know, the gcc build doesn't finish when switching default to higher than sm_35, so there's little point to go to a multilib setup at this point. But once we fix that, we could reconsider, otherwise, things are likely to regress again. Thanks, - Tom