From: Al Viro <viro@ZenIV.linux.org.uk>
To: linux-kernel@vger.kernel.org
Cc: David Miller <davem@davemloft.net>,
Dmitry Kasatkin <dmitry.kasatkin@intel.com>
Subject: sparc32 vs lib/mpi
Date: Sat, 21 Jan 2012 01:12:43 +0000 [thread overview]
Message-ID: <20120121011243.GC23916@ZenIV.linux.org.uk> (raw)
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...
next reply other threads:[~2012-01-21 1:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 1:12 Al Viro [this message]
2012-01-25 11:05 ` sparc32 vs lib/mpi Kasatkin, Dmitry
2012-01-26 22:02 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120121011243.GC23916@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=davem@davemloft.net \
--cc=dmitry.kasatkin@intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.