linux-kernel - Re: sparc32 vs lib/mpi

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] [day] [month] [year] [list]

Message-Id: <20120126.170204.2031178865806155061.davem@davemloft.net>
Date:	Thu, 26 Jan 2012 17:02:04 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	viro@...IV.linux.org.uk
Cc:	linux-kernel@...r.kernel.org, dmitry.kasatkin@...el.com
Subject: Re: sparc32 vs lib/mpi

From: Al Viro <viro@...IV.linux.org.uk>
Date: Sat, 21 Jan 2012 01:12:43 +0000

> 	I realize that very few people care about sparc32 these days,
> but...
> 	a) __clz_tab[] is defined (with identical contents) in
> lib/mpi/mpi-bit.c and arch/sparc/lib/divdi3.S.  Linker is unhappy,
> of course...
> 	b) the same thing ends up using __udiv_qrnnd(), which simply
> does not exist on sparc32.  There's a Cthulhu-scaring cascade of
> ifdefs in lib/mpi/longlong.h, with several variants of udiv_qrnnd()
> for sparc.  Unfortunately, it falls back on use of __udiv_qrnnd()...
> Note that arch/sparc/math-emu/sfp-util_32.h has a definition of
> udiv_qrnnd() which might match one of inline assembly variants in
> lib/mpi/longlong.h.  Or not.  BTW, what the hell is LONGLONG_STANDALONE?
> 
> 	Could somebody who might remember still remember that stuff
> come up with comments?  For now I'm disabling everything from
> INTEGRITY_SIGNATURE down to MPILIB on sparc32 cross-build, but it
> would be nice to get it at least somewhat sorted out...

I'm taking a look at this.
--
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/