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/30110] New: [gdb/testsuite] Test i386 test-cases on x86_64
Date: Fri, 10 Feb 2023 09:41:56 +0000 [thread overview]
Message-ID: <bug-30110-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30110
Bug ID: 30110
Summary: [gdb/testsuite] Test i386 test-cases on x86_64
Product: gdb
Version: HEAD
Status: NEW
Severity: enhancement
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
What is the status of x86_64/-m32 and i386 testing?
The sourceware builder lists one i386 bot, which is great. But of course that
only tests a few test-cases.
On biarch distros we can test target board unix/-m32, which I occasionally do
(because the opensuse gdb package testsuite uses that as a flavour in its test
matrix for x86_64: {-m64,-m32}x{-pie,-no-pie}).
I'm not sure if any other gdb maintainer (regularly, completely) tests
x86_64/-m32 or native i386.
An idea to improve test coverage is to include the i386-specific test-cases in
an x86_64 run, using -m32, if supported.
The drawback is that these test-case would be executed twice without increasing
test coverage in a setting where we'd do both -m32 and -m64 testing.
But the benefit would be that these test-cases do get exercised regularly in
any default x86_64 build & test scenario.
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2023-02-10 9:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-30110-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).