From: Sam James <sam@gentoo.org>
To: Alan Modra <amodra@gmail.com>
Cc: Tom Tromey <tom@tromey.com>,
aburgess@redhat.com, gdb-patches@sourceware.org
Subject: Re: sim regen preparation
Date: Wed, 16 Aug 2023 04:51:13 +0100 [thread overview]
Message-ID: <87y1iby78s.fsf@gentoo.org> (raw)
In-Reply-To: <ZNw9jG/7XJN1JoL4@squeak.grove.modra.org>
Alan Modra via Gdb-patches <gdb-patches@sourceware.org> writes:
> On Mon, Aug 14, 2023 at 10:26:12AM -0600, Tom Tromey wrote:
> [...]
>
> Note that people might have thought they were testing sim, but "make
> check" in sim doesn't do much unless you set up site-sim-config.exp,
> or have a lot of AS_FOR_TARGET_$arch, LD_FOR_TARGET_$arch and
> CC_FOR_TARGET_$arch in your environment. Also, linker warnings render
> many of the tests "UNTESTED". Only the latter is fixed, and of course
> only for current warnings.
This sounds like something we should probably dump into the wiki at some
point.
next prev parent reply other threads:[~2023-08-16 3:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 11:58 Alan Modra
2023-08-14 16:26 ` Tom Tromey
2023-08-16 3:07 ` Alan Modra
2023-08-16 3:51 ` Sam James [this message]
2023-08-16 13:20 ` Alan Modra
2023-08-16 17:47 ` Tom Tromey
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=87y1iby78s.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=aburgess@redhat.com \
--cc=amodra@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).