[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <de9e7ddf.dNq.dMV.1U.cxrGEd@mailjet.com>
Date: Sat, 22 Nov 2014 21:54:06 +0100
From: Joakim Sindholt <opensource@...sha.com>
To: musl@...ts.openwall.com
Subject: Re: [PATCH] arm assembly changes for clang compatibility
On Fri, 2014-11-07 at 08:26 -0500, Rich Felker wrote:
> On Fri, Nov 07, 2014 at 11:48:05AM +0100, Joakim Sindholt wrote:
> > On Fri, 2014-11-07 at 10:37 +0100, Luca Barbato wrote:
> > > On 06/11/14 23:38, Joakim Sindholt wrote:
> > > > + .word 0xecbc8b10 /* vldmia ip!, {d8-d15} */
> > >
> > > clang is already notified?
> > >
> > > lu
> >
> > I'm not sure what you mean. There isn't a bug in clang as it will
> > happily accept "vldmia ip!, {d8-d15}". It just won't accept "ldc p11,
> > cr8, [ip], #64" because that's not a legal instruction. Musl just uses
> > it because it aliases to the former and gas won't complain about missing
> > ARM features.
>
> Yes, the problem is that we can't use the official mnemonic because
> the assembler will reject it when the target model lacks fpu, and we
> can't use the generic coprocessor mnemonic because ARM and clang
> intentionally removed support for it. :(
>
> Rich
Any chance of getting this committed or is there more work to be done
and discussions to be had?
This is the only change needed to get musl working on ARM clang.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
