From: Jan Beulich <jbeulich@suse.com>
To: Mark Harmstone <mark@harmstone.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH 2/2] gas/testsuite: Add -gcodeview test for aarch64-w64-mingw32
Date: Thu, 26 Jan 2023 10:29:08 +0100 [thread overview]
Message-ID: <9bb526e7-fe3d-83cb-068e-f39aa01b67a8@suse.com> (raw)
In-Reply-To: <20230126003820.28482-2-mark@harmstone.com>
On 26.01.2023 01:38, Mark Harmstone wrote:
> This is a copy of the x86 gas -gcodeview test, with changes made for the
> differing instruction lengths between x86 and aarch64.
Hmm, probably okay for the time being, but going this route doesn't really
scale. For Dwarf we also have testcases covering multiple architectures in
one go ...
Jan
next prev parent reply other threads:[~2023-01-26 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 0:38 [PATCH 1/2] gas: Add CodeView constant for aarch64 Mark Harmstone
2023-01-26 0:38 ` [PATCH 2/2] gas/testsuite: Add -gcodeview test for aarch64-w64-mingw32 Mark Harmstone
2023-01-26 9:29 ` Jan Beulich [this message]
2023-01-26 9:26 ` [PATCH 1/2] gas: Add CodeView constant for aarch64 Jan Beulich
2023-01-26 12:41 ` Mark Harmstone
2023-01-26 12:53 ` Jan Beulich
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=9bb526e7-fe3d-83cb-068e-f39aa01b67a8@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=mark@harmstone.com \
/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).