From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3B97B3851898; Fri, 18 Nov 2022 16:01:11 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3B97B3851898 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1668787271; bh=rZgagEtVuHg1b7R4fMdnWwIbcG16FUD2EZpMagcI19Y=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ZLIoqQZs6QRgu7d/BBdZfHzXNORHI4Dzae29XqVHWik+sMQX/oeyQ7z5z7wtsaAml U+6hwh56ILRPlaa1nkiwPL4Ueo4DLfemj9ShFLE+kWO1ZKKbjMM9fnlsXEPclKQi9L HVhI8VdH44XjnRQXS7ylZBEKhJZ+6Ow+23Bw7Si8= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tdep/29804] [gdb/tdep, vax] Remove gdbarch_deprecated_function_start_offset Date: Fri, 18 Nov 2022 16:01:10 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29804 --- Comment #4 from Tom de Vries --- (In reply to Tom Tromey from comment #3) > If we had a VAX executable, would that be enough to > test any proposed change? I'm not sure I understand your question, possibly I'm missing some context related to vax, but my understanding is that in order to test a potential p= atch we'd need to be able to run the gdb testsuite on vax without and with the patch, to make sure we don't introduce regressions. --=20 You are receiving this mail because: You are on the CC list for the bug.=