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 C1302383A32D for ; Fri, 3 Jun 2022 06:53:41 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org C1302383A32D 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 89EB121BCE; Fri, 3 Jun 2022 06:53:40 +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 69BCB13AA2; Fri, 3 Jun 2022 06:53:40 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id Hl+XGPSvmWKYQwAAMHmgww (envelope-from ); Fri, 03 Jun 2022 06:53:40 +0000 Message-ID: <617cf9fe-9aee-43e9-9241-cd813fda8ed7@suse.de> Date: Fri, 3 Jun 2022 08:53:40 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [PATCH v2 12/16] testsuite, fortran: fix info-types for intel compilers Content-Language: en-US To: "Kempke, Nils-Christian" , Andrew Burgess , "gdb-patches@sourceware.org" Cc: "JiniSusan.George@amd.com" References: <20220531092423.2361679-1-nils-christian.kempke@intel.com> <20220531092423.2361679-6-nils-christian.kempke@intel.com> <87o7zdd6ua.fsf@redhat.com> <1ef51d87-3e95-94b5-d12e-70d9646c4a16@suse.de> From: Tom de Vries In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, 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 X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2022 06:53:43 -0000 On 6/1/22 11:21, Kempke, Nils-Christian wrote: > > >> -----Original Message----- >> From: Tom de Vries >> Sent: Wednesday, June 1, 2022 7:25 AM >> To: Andrew Burgess ; Kempke, Nils-Christian > christian.kempke@intel.com>; gdb-patches@sourceware.org >> Cc: JiniSusan.George@amd.com >> Subject: Re: [PATCH v2 12/16] testsuite, fortran: fix info-types for intel >> compilers >> >> On 5/31/22 18:06, Andrew Burgess via Gdb-patches wrote: >>> Nils-Christian Kempke writes: >>> >>>> This info-types.exp test case had a few issues that this patch fixes. >>>> >> >> I'm seeing this regression: >> ... >> Running >> /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.fortran/info- >> types.exp >> ... >> gdb compile failed, >> /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.fortran/info- >> types.f90:47:13: >> >> type (m1t1) :: var_b >> 1 >> Error: Derived type 'm1t1' at (1) is being used before it is defined >> /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.fortran/info- >> types.f90:50:8: >> >> var_b%b = 2 >> 1 >> Error: Symbol 'var_b' at (1) has no IMPLICIT type >> UNTESTED: gdb.fortran/info-types.exp: failed to prepare >> ... >> >> Likewise for a few other test-cases that use the same source. >> >> Thanks, >> - Tom > > Hi Tom, > > Sorry for this, too. I did not change the executable - nor the actual > compilation of it I think but this must be the source of the regressions. > > I made one of the checks in the info-types.exp file optional, but that does > not really explain the problems you are seeing.. > > I cannot reproduce this currently. I assume this is from a native run? Does > this also happen in the tests when ran individually? Or is this failure related > to the regressions seen because of the compiler_info caching? > Hi Nils, I've not been able to reproduce this anymore. I'm gonna assume that this was due to an incorrect temporary fix I was trying out. I currently just have a patch in my master-local branch that disables compiler_info caching, and that seems to work fine. Sorry for the noise. Thanks, - Tom