From: William Cohen <wcohen@redhat.com>
To: Crestez Dan Leonard <cdleonard@gmail.com>
Cc: systemtap@sourceware.org
Subject: Re: What about MIPS support?
Date: Thu, 06 Aug 2015 01:30:00 -0000 [thread overview]
Message-ID: <55C2B8CB.3060700@redhat.com> (raw)
In-Reply-To: <CAJdmCrLN3w6J3XHTCx0uMDQDAc6LB+5qC3o7Rr+KABAriwNATg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
On 08/05/2015 02:45 PM, Crestez Dan Leonard wrote:
> Hello,
>
> Those patches were on top of an older version. I just rebased on top of latest release 2.8 and only encountered a minor conflict. There are no further conflicts when rebasing on top of latest master. I pushed the branches here:
>
> https://github.com/cdleonard/systemtap/commits/mips-2.8
> https://github.com/cdleonard/systemtap/commits/mips-master
>
> Regards,
> Leonard
Hi Leonard,
Thanks for the pointers to current git trees with the patches. I found that the div instruction for the mips processor is not coded correctly and the "make installcheck" smoke test fails as a result. Attached is a patch to fix that and allow the systemtap.base/arith.exp test to pass. With this patch the mips-master branch will run the "make installcheck" testsuite on a 32-bit mips processor
-Will
[-- Attachment #2: mips_div_asm.patch --]
[-- Type: text/x-patch, Size: 948 bytes --]
diff --git a/runtime/linux/arith.c b/runtime/linux/arith.c
index 9f65711..9de9bb6 100644
--- a/runtime/linux/arith.c
+++ b/runtime/linux/arith.c
@@ -252,12 +252,14 @@ typedef union
#elif defined (__mips__)
-#define umul_ppmm(w1, w0, u, v) \
- __asm__ ("multu %2,%3" \
- : "=l" ((USItype) (w0)), \
- "=h" ((USItype) (w1)) \
- : "d" ((USItype) (u)), \
- "d" ((USItype) (v)))
+#define umul_ppmm(w1, w0, u, v) \
+ __asm__ ("multu %2,%3\n" \
+ "mflo %0\n" \
+ "mfhi %1\n" \
+ : "=d" ((USItype) (w0)), \
+ "=d" ((USItype) (w1)) \
+ : "d" ((USItype) (u)), \
+ "d" ((USItype) (v)))
#if !defined (sub_ddmmss)
#define sub_ddmmss(sh, sl, ah, al, bh, bl) \
next prev parent reply other threads:[~2015-08-06 1:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 20:04 Victor Kamensky
2012-08-23 2:23 ` Maneesh Soni
2012-08-23 14:33 ` Ananth N Mavinakayanahalli
2012-08-23 22:11 ` Josh Stone
2012-10-15 21:21 ` Victor Kamensky
2012-10-23 23:43 ` Josh Stone
2015-08-05 12:42 ` William Cohen
[not found] ` <CAJdmCr+1s6JLW3DsGxbdqPcpnD1+wNo5VwAifm6UN-SWE+PKmw@mail.gmail.com>
2015-08-05 16:25 ` William Cohen
[not found] ` <CAJdmCrLN3w6J3XHTCx0uMDQDAc6LB+5qC3o7Rr+KABAriwNATg@mail.gmail.com>
2015-08-06 1:30 ` William Cohen [this message]
2015-08-06 13:04 ` William Cohen
-- strict thread matches above, loose matches on Subject: below --
2012-08-17 16:33 Hallsmark, Per
2012-08-18 2:20 ` Josh Stone
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=55C2B8CB.3060700@redhat.com \
--to=wcohen@redhat.com \
--cc=cdleonard@gmail.com \
--cc=systemtap@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).