mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Wermut <wermut@gmail.com>
To: musl@lists.openwall.com
Subject: Re: thumb2 support
Date: Tue, 29 Apr 2014 18:09:14 +0200	[thread overview]
Message-ID: <CALONj1dDT5rJvWyZ9kNorqzRNTsR5QhRUiqi4GZcjnaZzZk1qw@mail.gmail.com> (raw)
In-Reply-To: <SNT146-W31A02BE75C17D9ABA0099A8460@phx.gbl>

Hi

I have tested the patch from Stephen Thomas at least for gcc 4.6, 4.7
and 4.8. Seems to work. Would be nice if the 1.1.1 release will
include a fix.

Regards
Kevin

On Tue, Apr 29, 2014 at 3:14 AM, Stephen Thomas <scjthm@live.com> wrote:
>> On Tue, Apr 29, 2014 at 12:52:36AM +0100, Stephen Thomas wrote:
>> > I remember that the old thumb didn't support the conditional
>> > instructions and was quite slow. I only care about thumb2 and am
>> > currently using gcc, so I attach a patch for the thumb that will
>>
>> The code here is only used on armv6/v7. Do any such chips lack thumb2?
>> If there's any doubt, we could look at what gcc generates for the
>> __sync_* builtins in thumb mode.
>>
>> > only work for gcc .
>>
>> Why is it only for gcc?
>
> I have only tested with gcc. I don't know what llvm nor armcc do.  Is there
> an ASM standard like ther is for C/C++/fortran? There is some good info on
> thumb here, https://wiki.ubuntu.com/ARM/Thumb2 and the various ways of
> supporting ARM. I guess that the thumb2 could be replaced by a __thumb__.
>
>>
>> > I think that gcc builds two versions of atomic
>>
>> What do you mean by this?
>
> I am building the native toolchain as I would like to run this on an
> embedded platform. My understanding is that when you build the toolchain you
> need to provide somethings that end up going in libgcc_s.so such as
> threading if you are using openmp in C++. etc etc. That patch works for both
> the -marm and -mthumb or whatever the thumb targets are.
>
>>
>> > so the ugly #define was needed. I cannot remember what rvct/rvds or
>> > whatever it is branded as these days uses, but from memory old
>> > versions didn't support the gnu assebmly syntax.
>>
>> All asm in musl is gas syntax so this is nothing new.
>>
>> Rich


  reply	other threads:[~2014-04-29 16: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 [this message]
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

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=CALONj1dDT5rJvWyZ9kNorqzRNTsR5QhRUiqi4GZcjnaZzZk1qw@mail.gmail.com \
    --to=wermut@gmail.com \
    --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).