From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: status of armhf asm with VFP instructions
Date: Thu, 15 Oct 2015 21:03:46 -0400 [thread overview]
Message-ID: <20151016010346.GC8645@brightrain.aerifal.cx> (raw)
In-Reply-To: <20151016003313.GZ10551@port70.net>
On Fri, Oct 16, 2015 at 02:33:13AM +0200, Szabolcs Nagy wrote:
> * Rich Felker <dalias@libc.org> [2015-10-15 20:00:56 -0400]:
> > On Fri, Oct 16, 2015 at 01:16:07AM +0200, Szabolcs Nagy wrote:
> > > most likely ual is the long term solution.
> > >
> > > maybe it is best to switch to ual and then write that script
> > > if ppl with old binutils run into issues.
> >
> > That sounds like it might be the best option. I don't like dropping
> > support for old stuff, but ARM really made a mess of this by making a
> > new gratuitously incompatible asm syntax and encouraging tools not to
> > support the old syntax (and particularly, not to support generating
> > thumb2 from it, despite the fact that there's no fundamental reason it
> > couldn't be done).
> >
> > BTW for other things I think we need some sort of syntax directive to
> > tell the assembler we'll be using the unified syntax -- is this right?
> > Do you know what the minimum gas version that supports this directive
> > is?
>
> ..syntax unified (binutils supports it since 2005).
Hm? That would include 2.17. So is the new vfp syntax separate from
UAL-vs-legacy?
> and the default is divided syntax
> (so inline asm has to use divided syntax or
> ".sytax unified"
> ....
> ".syntax divided")
Uhg, and it's the opposite for clang with integrated assembler, right?
Thankfully most instructions you'd actually use look the same either
way...
Rich
next prev parent reply other threads:[~2015-10-16 1:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 22:33 Szabolcs Nagy
2015-10-15 22:44 ` Rich Felker
2015-10-15 23:16 ` Szabolcs Nagy
2015-10-15 23:58 ` Szabolcs Nagy
2015-10-19 6:12 ` Rich Felker
2015-10-16 0:00 ` Rich Felker
2015-10-16 0:33 ` Szabolcs Nagy
2015-10-16 1:03 ` Rich Felker [this message]
2015-10-16 3:23 ` Rich Felker
2015-10-16 6:42 ` Khem Raj
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=20151016010346.GC8645@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).