public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-30122-4717@http.sourceware.org/bugzilla/> (raw)

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

            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 compiler
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 analysis.

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

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

             reply	other threads:[~2023-02-14 13:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 13:36 vries at gcc dot gnu.org [this message]
2023-02-14 13:36 ` [Bug cli/30122] " vries at gcc dot gnu.org
2023-02-15  9:37 ` vries at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-30122-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).