Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
To: Stafford Horne <shorne@gmail.com>
Cc: GDB patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/2] sim: testsuite: Get common tests compiling again
Date: Sat, 3 Apr 2021 16:01:34 -0400	[thread overview]
Message-ID: <YGjJntD2L9jvyTBW@vapier> (raw)
In-Reply-To: <20210201064457.GI2002709@lianli.shorne-pla.net>

On 01 Feb 2021 15:44, Stafford Horne via Gdb-patches wrote:
> On Sun, Jan 31, 2021 at 10:15:02PM -0500, Mike Frysinger wrote:
> > On 05 Oct 2017 23:17, Stafford Horne wrote:
> > > This is a series of changes to the the old and non working sim common
> > > testsuite .  As far as I can tell this has not been used since what
> > > looks like before 64-bit desktop computers became common.  Most of the
> > > changes here are to convert the test code to be 64-bit portable.
> > 
> > sorry for not seeing this sooner.  i stumbled across this dir myself
> > recently and came to the same conclusions you did (about the non-fpu
> > stuff).  i pushed some fixes to get it working on my 64-bit desktop.
> > 
> > i haven't tried to integrate the build though.  i was going to let
> > that wait until we had better overall build integration than add some
> > more subdir-configure scripts, then should be able to revisit.
> 
> OK.
> 
> > > The fpu-tst tool actually depends on external code from v2 of berkeley
> > > softfloat [1] and testfloat [2] libraries which I cleaned up so the
> > > would actually build on a modern compiler.  The build will generate a
> > > 'testfloat' binary which will be used to compare the sim-fpu vs the
> > > softfloat implementation.
> > 
> > ah, very cool.  i saw those includes and thought those were weird but
> > then gave up on trying to track them down.  i assumed it was some weird
> > thing that didn't exist anymore.
> > 
> > can you refresh these and see how many are still needed ?  i think the
> > alu-tst & bits-gen & bits-tst files should be all set now in the latest
> > tree.  for the fpu-tst, how about we put the details/comments into the
> > source file itself for now ?
> 
> Sure, it will take me some time to get done.

i've done a bit more work in here and the tests are part of `make check` now.
hopefully the new sim/testsuite/common/local.mk is easier to work with.
-mike

  reply	other threads:[~2021-04-03 20:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05 14:17 [PATCH 0/2] Revive sim common tests Stafford Horne
2017-10-05 14:18 ` [PATCH 2/2] sim: testsuite: Add configure.ac and configure Stafford Horne
2017-10-05 14:18 ` [PATCH 1/2] sim: testsuite: Get common tests compiling again Stafford Horne
2021-02-01  3:15   ` Mike Frysinger via Gdb-patches
2021-02-01  6:44     ` Stafford Horne via Gdb-patches
2021-04-03 20:01       ` Mike Frysinger via Gdb-patches [this message]
2021-04-03 20:44         ` Stafford Horne via Gdb-patches

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=YGjJntD2L9jvyTBW@vapier \
    --to=gdb-patches@sourceware.org \
    --cc=shorne@gmail.com \
    --cc=vapier@gentoo.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