Displaying 6 results from an estimated 6 matches for "__arm_eabi__".
2014 Sep 05
5
[LLVMdev] [Compiler-RT] [ARM] Where __aeabi_[il]div0 builtins should be implemented?
Hi,
There are several places in compiler-rt which refer to __aeabi_idiv0.
For example, in lib/builtins/arm/udivsi3.S:
#ifdef __ARM_EABI__
b __aeabi_idiv0
#else
JMP(lr)
#endif
At the same time there is no definition of it. It looks as if it was
done intentionally so that third-party could provide custom handler for
division by zero.
IMHO It's not very consistent and looks odd as all other __aebi_*
functions are provided...
2006 Jun 26
0
[klibc 22/43] arm support for klibc
...-0,0 +1,61 @@
+/*
+ * arch/arm/syscall.S
+ *
+ * System call common handling
+ */
+
+ .type __syscall_common,#function
+ .globl __syscall_common
+#ifndef __thumb__
+ /* ARM version - this is executed after the swi, unless
+ we are compiled in EABI mode */
+
+ .balign 4
+__syscall_common:
+#ifdef __ARM_EABI__
+ ldr r4, [sp,#16]
+ ldr r5, [sp,#20]
+ ldr r7, [lr]
+ swi 0
+#endif
+ cmn r0, #4096
+ rsbcs r2, r0, #0
+ ldrcs r3, 1f
+ mvncs r0, #0
+ strcs r2, [r3]
+ ldmfd sp!,{r4,r5,r7,pc}
+
+ .balign 4
+1:
+ .word errno
+
+#else
+ /* Thumb version - must still load r4 an...
2014 Sep 06
2
[LLVMdev] [Compiler-RT] [ARM] Where __aeabi_[il]div0 builtins should be implemented?
> Looks as though whomever implemented the call to __aeabi_idiv0 wanted
> to be conservative for non EABI targets.
How could it prevent him from providing default implementation of
__aeabi_idiv0() for EABI targets?
> AFAIK, gnueabi targets recognize all EABI functions, so that should
> work well.
Not sure I understand you, nothing in compiler-rt defines these
functions, they are
2014 Sep 06
3
[LLVMdev] [Compiler-RT] [ARM] Where __aeabi_[il]div0 builtins should be implemented?
...04:48:20AM -0700, Renato Golin wrote:
> I'm in favour for adding them ASAP, but we might need an ifdef to avoid
> creating unnecessary (or conflicting) symbols for non-EABI targets.
Sure, it makes sense.
> A proper solution would be to have:
>
> LOCAL_LABEL(divby0):
> #ifdef __ARM_EABI__
> b __aeabi_idiv0
> #else
> mov r0, #0
> JMP(lr)
> #endif
>
> And make both __aeabi_{i,l}div0 return 0.
>
> I'm hoping both parts of the ifdef to generate *identical* code, but
> with the benefit that we can change the behaviour of div0 by
> overriding the...
2014 Sep 06
2
[LLVMdev] [Compiler-RT] [ARM] Where __aeabi_[il]div0 builtins should be implemented?
...tation
in SVN r217322.
>
> Cheers,
>
> Jon
>
>
> On 9/5/14, 12:10 PM, Sergey Dmitrouk wrote:
>
>> Hi,
>>
>> There are several places in compiler-rt which refer to __aeabi_idiv0.
>> For example, in lib/builtins/arm/udivsi3.S:
>>
>> #ifdef __ARM_EABI__
>> b __aeabi_idiv0
>> #else
>> JMP(lr)
>> #endif
>>
>> At the same time there is no definition of it. It looks as if it was
>> done intentionally so that third-party could provide custom handler for
>> division by zero.
>>
>> IM...
2006 Jun 28
35
[klibc 00/31] klibc as a historyless patchset (updated and reorganized)
I have updated the klibc patchset based on feedback received. In
particular, the patchset has been reorganized so as not to break
git-bisect.
Additionally, this updates the patch base to 2.6.17-git12
(d38b69689c349f35502b92e20dafb30c62d49d63) and klibc 1.4.8; the main
difference on the klibc side is removal of obsolete code.
This is also available as a git tree at: