lkml.org 
[lkml]   [2014]   [Oct]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH v5 29/29] nios2: Build infrastructure
From
On Tue, Oct 28, 2014 at 9:38 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Friday 24 October 2014 16:24:31 Ley Foon Tan wrote:
>> +DECLARE_EXPORT(__gcc_bcmp);
>> +DECLARE_EXPORT(__divdi3);
>> +DECLARE_EXPORT(__divsi3);
>> +DECLARE_EXPORT(__moddi3);
>> +DECLARE_EXPORT(__modsi3);
>> +DECLARE_EXPORT(__udivdi3);
>> +DECLARE_EXPORT(__udivmoddi4);
>> +DECLARE_EXPORT(__udivsi3);
>> +DECLARE_EXPORT(__umoddi3);
>> +DECLARE_EXPORT(__umodsi3);
>> +DECLARE_EXPORT(__muldi3);
>>
>
> I don't remember what all of these are, but at least some of them seem
> to be concerned with 64-bit division. By convention, we don't provide those
> in the Linux kernel but instead require all code to use the do_div()
> macro instead.
Do you mean kernel doesn't support 64 bit division result for a 32-bit
architecture? Because do_div() only support 32-bit division result for
32-bit architecture.
Compiler will auto generate call to __divdi3() for the following
example code. This means loadable module will have compilation error
if we don't export symbol for __divdi3, but built-in module is fine.
Is this an expectation? Or we can keep 64-bit division symbols here
since they are no harm (they are software emulation when without
hardware divider).

long long a, b, c;
a = b / c;

Regards
Ley Foon


\
 
 \ /
  Last update: 2014-10-30 12:01    [W:0.151 / U:0.076 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site