From: Bobby Bingham <koorogi@koorogi.info>
To: musl@lists.openwall.com
Subject: Re: mips n64 porting review
Date: Mon, 22 Feb 2016 08:16:26 -0600 [thread overview]
Message-ID: <20160222141626.GB12348@dora.lan> (raw)
In-Reply-To: <DE16056458B9894F9D46202EC1BBB28B3BE15ED6@PUMAIL01.pu.imgtec.org>
On Mon, Feb 22, 2016 at 10:06:02AM +0000, Mahesh Bodapati wrote:
> Hi Rich,
> I have attached the patch which has all the MIPS n64 porting work. I have created mipsn64port_review remote branch on GitHub and please have a look at
> https://github.com/MaheshBodapati/musl/commits/mipsn64port_review which has the broken down patches and the base revision on which we have prepared patch is d150764
>
I've only looked at some of the code, but I have some initial
comments/questions.
- In atomic_arch.h, you shouldn't need to implement all those
functions. Take a look at the current 32-bit mips file. You should
probably be able to just implement a_ll, a_sc, a_barrier, a_pre_llsc,
a_post_llsc, and a_cas_p.
I have a patch I'm working on that would let 64-bit ll/sc archs like
mips64 and powerpc64 implement 64-bit variants of a_ll/a_sc and have
src/internal/atomic.h implement a_cas_p and some of the other 64-bit
operations in terms of those primitives, which should further
simplify this file. I'll try to get this patch cleaned up and
submitted tonight.
- In bits/signal.h, is the union in fpregset_t correct for both big and
little endian?
- In pthread_arch.h, what instruction is that 0x7c03e83b? I see this
same code is present in the existing musl mips32 port, but IMHO it
could use a comment identifying the instruction.
- In syscall_arch.h, are the definitions of __SYSCALL_LL_E/O correct?
Those macros exist because some 32-bit architectures pass 64-bit
system call parameters in even/odd register pairs, even if there is
an unused odd numbered register. On 64-bit architectures, where
long long fits inside a single register, I would expect these to both
be defined to (x)
- I'm sure about the changes in ldso/dynlink.c. One of them seems to
change the whitespace to be more misleading, and one reorders two
lines for no apparent reason. I'm not sure the purpose of the
remaining hunk.
--
Bobby
next prev parent reply other threads:[~2016-02-22 14:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 10:06 Mahesh Bodapati
2016-02-22 14:16 ` Bobby Bingham [this message]
2016-02-23 3:32 ` Rich Felker
[not found] ` <CAKd0kD+qQhvhiuaQ483ds2KyGD5qFjqJg4pOT6GyqCaoR9_auA@mail.gmail.com>
[not found] ` <DE16056458B9894F9D46202EC1BBB28B3BE16033@PUMAIL01.pu.imgtec.org>
2016-02-24 10:11 ` Jaydeep Patil
2016-02-24 17:53 ` dalias
2016-02-25 8:21 ` Jaydeep Patil
[not found] ` <DE16056458B9894F9D46202EC1BBB28B3BE162B3@PUMAIL01.pu.imgtec.org>
2016-02-25 12:05 ` Jaydeep Patil
2016-02-25 18:01 ` dalias
2016-02-25 18:22 ` dalias
2016-02-26 3:58 ` Jaydeep Patil
2016-02-25 18:23 ` Szabolcs Nagy
2016-02-25 18:29 ` Szabolcs Nagy
2016-02-25 18:31 ` Rich Felker
[not found] <DE16056458B9894F9D46202EC1BBB28B3BDC3210@PUMAIL01.pu.imgtec.org>
2016-02-03 23:36 ` Rich Felker
2016-02-04 0:45 ` Szabolcs Nagy
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=20160222141626.GB12348@dora.lan \
--to=koorogi@koorogi.info \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).