From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id aFuvMiLY5mfztR0AWB0awg (envelope-from ) for ; Fri, 28 Mar 2025 13:10:58 -0400 Received: by simark.ca (Postfix, from userid 112) id CB05B1E0C3; Fri, 28 Mar 2025 13:10:58 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.3 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED autolearn=unavailable autolearn_force=no version=4.0.1 Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 833071E0C0 for ; Fri, 28 Mar 2025 13:10:58 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 30C5E3830606 for ; Fri, 28 Mar 2025 17:10:58 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 30C5E3830606 Received: from angie.orcam.me.uk (angie.orcam.me.uk [78.133.224.34]) by sourceware.org (Postfix) with ESMTP id 871CF3830615 for ; Fri, 28 Mar 2025 17:10:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 871CF3830615 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=orcam.me.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=orcam.me.uk ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 871CF3830615 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=78.133.224.34 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1743181800; cv=none; b=NpW9c9pcIKFw0COPZIxSW1M8ig6SCJKGyLetc1ik+lTDO2HcWnc0FkxgkDhpjSzZyjBAyIzDEHQSLiuHyA5gYeg0dxn6v3ePVmY0dT3vwdecXw+926VF/UGZEzGWaM2u931LyWPC8sxxgPAGWAoyd7Gg4dlFHqSk6Z5P9z3LlQk= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1743181800; c=relaxed/simple; bh=vQ/CTkTvQsan/jN/O70tjEA+yKerPghNzaT2keU0K6w=; h=Date:From:To:Subject:Message-ID:MIME-Version; b=SYhlcC4NZJbRzwdS/KJ/GfTQSrnkO3y/U6c3+Qy6eS2DD+InmGIbWSAnn73IwLkFMIf/RAdiUnjo8/1q/8AHxKqyTNzFp78zCiU/LJ5IvgrbSw6OIZNceGGDMgwqZ80u2cchJtBUqGNEU53XbzVy7+6pYRKlOMKHMwp11hqV7/M= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 871CF3830615 Received: by angie.orcam.me.uk (Postfix, from userid 500) id 5DB5292009C; Fri, 28 Mar 2025 18:09:59 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id 57B2B92009B; Fri, 28 Mar 2025 17:09:59 +0000 (GMT) Date: Fri, 28 Mar 2025 17:09:59 +0000 (GMT) From: "Maciej W. Rozycki" To: Milica Matic cc: Djordje Todorovic , Milos Kalicanin , Simon Marchi , Chao-ying Fu , Andrew Burgess , Kevin Buettner , Thomas Bogendoerfer , gdb-patches@sourceware.org Subject: Re: [PATCH v12 2/2] gdb: mips: Add MIPSR6 support In-Reply-To: Message-ID: References: <20250219130125.356900-1-milica.matic@htecgroup.com> <20250219130125.356900-4-milica.matic@htecgroup.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces~public-inbox=simark.ca@sourceware.org On Sun, 2 Mar 2025, Maciej W. Rozycki wrote: > This all also means I can use the R3400 system to reliably verify GDB > changes and will proceed with your submission once I'm back from my > holiday in a fortnight's time. Meanwhile I do hope this analysis helps. I have regression-tested your change now and while the problem previously noted persists with `call-ar-st' and `varargs' tests, leaving them stuck forever in a weird state: macro 1299 0.0 0.0 0 0 ? XW Mar24 0:03 [call-ar-st] macro 4501 0.0 0.0 0 0 ? XW Mar24 0:05 [varargs] results are looking good otherwise, except for the newly-added R6 case: Running .../gdb/testsuite/gdb.arch/mips-64-r6.exp ... gdb compile failed, Assembler messages: Fatal error: can't create .../gdb/testsuite/gdb.arch/mips-64-r60.o: No such file or directory DUPLICATE: gdb.arch/mips-64-r6.exp: failed to prepare This is because there's no output directory present for the object file requested: there's no gdb.arch/ under .../gdb/testsuite/. I reckon it's been many years already since our directory arrangement here was changed. Have you run your verification with the upstream trunk version of GDB? Also the duplicate failure message needs to be corrected as test messages are expected to be uniquely identifiable. Please update your patch accordingly and resubmit; meanwhile I'll have a detailed look at the backend updates. Maciej