[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <7CC703B4-FA8E-413E-BBFE-73E2107D36EF@gmail.com>
Date: Mon, 19 Oct 2015 14:07:53 -0700
From: Khem Raj <raj.khem@...il.com>
To: musl@...ts.openwall.com
Subject: Re: [PATCH] convert arm memcpy asm to UAL, remove .word hacks
> On Oct 18, 2015, at 5:17 PM, Rich Felker <dalias@...c.org> wrote:
>
> I've found that, contrary to the message in commit
> 9367fe926196f407705bb07cd29c6e40eb1774dd, all relevant gas versions
> actually do support .syntax unified, and assemble memcpy.s
> successfully with the attached patch applied. If there are no
> objections I'd like to go ahead and commit it. The only remaining
> .word hacks I'm aware of are in setjmp and longjmp, but they may still
> be needed to avoid wrongly flagging plain EABI (softfloat) binaries
> as needing hard float.
IIRC .syntax should not affect the fp ABI assumptions, Its plainly for unifying arm/thumb-ness
in asm files and .eabi_attribute is the directive which could set FP ABI and I don’t see it
being set in asm file which means it will be set depending on compiler cmdline.
> I'd really like some feedback on what the issues
> with that are and how to best avoid problems. Hopefully we can make
> the transition to UAL syntax quickly in the next release cycle and get
> Cortex-M support (with the new ARM FDPIC ABI).
>
> Rich
> <arm-ual1.diff>
Download attachment "signature.asc" of type "application/pgp-signature" (205 bytes)
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.
