[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ab5fb134-1fb0-4fbe-d281-b3aeea55bb9c@codeaurora.org>
Date: Wed, 22 Jun 2016 17:21:54 -0700
From: "Zhao, Weiming" <weimingz@...eaurora.org>
To: musl@...ts.openwall.com
Subject: Re: build musl for armv7m
Fixed.
Btw, can we make exit() weak function? (patch attached)
This allows user code to redefine it because in baremetal environment,
sometime we want to customize it. For example, some code never exits, so
we can define a dummy exit() and thus save code size.
On 6/22/2016 4:26 PM, Rich Felker wrote:
> On Wed, Jun 22, 2016 at 01:37:38PM -0700, Zhao, Weiming wrote:
>> How about using the following test?
>>
>> !defined(__thumb__) || (__ARM_ARCH_7A__ || __ARM_ARCH_7R__ ||
>> __ARM_ARCH > 7)
>>
>> Because I think those instructions are ISA related, not just
>> arm/thumb. For example, using -mcpu=cortex-a8 -mthumb, the original
>> code still works. So if only testing __thumb__, the armv7-a thumb
>> mode will fall into the slow path too.
> I think perhaps __thumb2__ is what you're looking for...?
>
> Rich
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
View attachment "patch.diff" of type "text/plain" (1602 bytes)
View attachment "patch_exit.diff" of type "text/plain" (306 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.
