From: Khem Raj <raj.khem@gmail.com>
To: musl@lists.openwall.com
Subject: Re: [PATCH] convert arm memcpy asm to UAL, remove .word hacks
Date: Mon, 19 Oct 2015 14:07:53 -0700 [thread overview]
Message-ID: <7CC703B4-FA8E-413E-BBFE-73E2107D36EF@gmail.com> (raw)
In-Reply-To: <20151019001743.GA4363@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
> On Oct 18, 2015, at 5:17 PM, Rich Felker <dalias@libc.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>
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 204 bytes --]
next prev parent reply other threads:[~2015-10-19 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 0:17 Rich Felker
2015-10-19 21:07 ` Khem Raj [this message]
2015-10-19 21:15 ` 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=7CC703B4-FA8E-413E-BBFE-73E2107D36EF@gmail.com \
--to=raj.khem@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).