From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 04C8C3858D1E; Tue, 14 Feb 2023 13:36:16 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 04C8C3858D1E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1676381776;
	bh=MJPtxX4T/qtmrVVssg04iOz2TrDksIIWJlMIV8Ur2+s=;
	h=From:To:Subject:Date:From;
	b=XbUMzz26EVyXQptbazqYezsuDDnEPo85dZQIZz4OSJGgBav7bi2IhKlMD3A5BuXKU
	 v5RcqJPlcH6XoKLxiX45ZUkf0apAsTV3sl/K96D7HdZYYAlqGc4RupJiH4SzOYKPzC
	 P8QNjH6kVz1JykpH1aUX3iEon9P27HdiFfz7vAyQ=
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/30122] New: [gdb/cli] Add maint check-prologue
Date: Tue, 14 Feb 2023 13:36:15 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: testsuite
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: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-30122-4717@http.sourceware.org/bugzilla/>
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: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D30122

            Bug ID: 30122
           Summary: [gdb/cli] Add maint check-prologue
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I see two conflicting goals:
- we want the testsuite to check prologue analysis
- we don't want to test it in random test-cases, where the intention is
  to check other functionality, which depends on prologue analysis.
  It is both inconvenient and insufficient.

If there is a problem with the prologue analysis, that may be due to a comp=
iler
problem.  In another case, it maybe due to an architecture-specific specific
prologue analyzer.

I've been making test-cases less dependent on prologue analysis, to make
results more similar for different archs/compilers.

But we need to address the fact that this reduces testing of prologue analy=
sis.

I came up with the idea of making a command maint check-prologue that itera=
tes
over all the functions in an exec, calls both the architecture-specific
prologue analysis and the compiler-based prologue analysis and compares the=
n,
and prints a line per function where there's a mismatch.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=