From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: thumb2 support
Date: Sun, 4 May 2014 10:09:59 -0400 [thread overview]
Message-ID: <20140504140959.GA25506@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAK4o1WxSn_2meoXGXM+-WA4q4BCFrufAq2NC7KTjhS6rFJCieQ@mail.gmail.com>
On Sun, May 04, 2014 at 02:56:49PM +0100, Justin Cormack wrote:
> I was wrong, sorry, __thumb__ and __thumb2__ are defined. Maybe
> __ARM_ARCH_ISA_THUMB does seem to be not defined always.
OK, so the patch as committed should at least be ok, even if not
optimal.
> Some armv6 machines have thumb2, but not many (ARMv6T2 apparently, I
> don't have one I don't think).
In any case it's not broken on them, just using the kuser helpers
rather than inlines.
> All v7 machines do have (only) thumb2.
> So you could test ARM_ARCH_6T2 or __thumb2__.
We could change the !__thumb__ test to (!__thumb__||__thumb2__).
> Alternatively it seems you can compile with -Wa,-mimplicit-it=always
> and you don't need the patch at all. That could make it easier in
> future.
Yes, but it doesn't fix the fact that we have to omit the asm entirely
on thumb1. Also adding mandatory arch-specific CFLAGS is probably more
ugly than tucking away this logic in the arch-specific atomic.h file.
> So far all the thumb2-only hardware has no MMU, so less likely to be
> using musl...
And if it is using musl it will probably need a special
bare-metal-type port with its own asm dirs rather than using the
existing Linux/ARM asm. (Of course rdp has an approach that shares the
Linux asm and syscall framework despite being "bare-metal".)
Rich
prev parent reply other threads:[~2014-05-04 14:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 3:36 Stephen Thomas
2014-04-28 12:06 ` Szabolcs Nagy
2014-04-28 14:27 ` Rich Felker
2014-04-28 23:52 ` Stephen Thomas
2014-04-29 0:56 ` Rich Felker
2014-04-29 1:14 ` Stephen Thomas
2014-04-29 16:09 ` Wermut
2014-04-30 19:03 ` Rich Felker
2014-05-04 11:54 ` Justin Cormack
2014-05-04 12:01 ` Rich Felker
2014-05-04 13:56 ` Justin Cormack
2014-05-04 14:09 ` Rich Felker [this message]
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=20140504140959.GA25506@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).