From: "George Spelvin" <linux@horizon.com>
To: geert@linux-m68k.org, gregungerer@westnet.com.au,
linux-m68k@lists.linux-m68k.org, linux@horizon.com
Subject: Re: [RFC PATCH 1/2] arch/m68k/lib/mulsi3.S: Optimize]
Date: 12 May 2016 22:36:31 -0400 [thread overview]
Message-ID: <20160513023631.15160.qmail@ns.horizon.com> (raw)
In-Reply-To: <573528E8.8070301@westnet.com.au>
> I have many test setups for ColdFire (qemu and real hardware) but
> none of them actually use the mulsi3 code. I don't have anything
> for testing classic m68000 builds.
>
> So other than compiling it I don't have an easy way to currently
> test it.
You couldn't write a user-level test program which calls __mulsi3(x,y)
explicitly and compares the result to x*y?
I'll write it for you if you like.
Even if we can only test the ColdFire branch, that reduces the number
of untested lines considerably.
next prev parent reply other threads:[~2016-05-13 2:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 10:24 [RFC PATCH 1/2] arch/m68k/lib/mulsi3.S: Optimize] George Spelvin
2016-05-11 12:38 ` Greg Ungerer
2016-05-12 8:04 ` George Spelvin
2016-05-12 8:35 ` Andreas Schwab
2016-05-12 13:14 ` Greg Ungerer
2016-05-12 12:46 ` Greg Ungerer
2016-05-12 20:52 ` George Spelvin
2016-05-13 1:07 ` Greg Ungerer
2016-05-13 2:36 ` George Spelvin [this message]
2016-05-13 6:45 ` Greg Ungerer
2016-05-13 9:02 ` George Spelvin
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=20160513023631.15160.qmail@ns.horizon.com \
--to=linux@horizon.com \
--cc=geert@linux-m68k.org \
--cc=gregungerer@westnet.com.au \
--cc=linux-m68k@lists.linux-m68k.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