lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFiDJ59LZSwKBzVuuzfH_5772-BR74EH=d=FeBbWvEXjfpisug@mail.gmail.com>
Date:	Thu, 30 Oct 2014 18:44:37 +0800
From:	Ley Foon Tan <lftan@...era.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Linux-Arch <linux-arch@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	Chung-Lin Tang <cltang@...esourcery.com>
Subject: Re: [PATCH v5 29/29] nios2: Build infrastructure

On Tue, Oct 28, 2014 at 9:38 PM, Arnd Bergmann <arnd@...db.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ