From: Momchil Velikov <velco@fadata.bg>
To: Troy Benjegerdes <hozer@drgw.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Broken asm/div64.h macro
Date: 27 Jan 2002 00:51:42 +0200 [thread overview]
Message-ID: <87sn8sybcx.fsf@fadata.bg> (raw)
In-Reply-To: <20020126103720.Z14725@altus.drgw.net>
>>>>> "Troy" == Troy Benjegerdes <hozer@drgw.net> writes:
Troy> Our div64.h macro is quite broken, and causes printk to not be able to do
Troy> a long long format.
Troy> Is there a 'fast' generic C algorithm we can replace it with, instead of
Troy> mucking with ASM?
Hmm, I sent a patchlet to lkml with Subject: [PATCH] 64-bit divide tweaks.
Doesn't it work for you ?
Regards,
-velco
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-26 22:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-26 16:37 Broken asm/div64.h macro Troy Benjegerdes
2002-01-26 17:27 ` Geert Uytterhoeven
2002-01-26 22:30 ` Gabriel Paubert
2002-01-26 22:51 ` Momchil Velikov [this message]
2002-01-27 17:49 ` Troy Benjegerdes
2002-01-28 1:38 ` Kaoru Fukui
2002-01-28 8:16 ` Momchil Velikov
2002-01-28 15:28 ` Tom Rini
2002-01-28 19:45 ` Geert Uytterhoeven
2002-01-29 0:37 ` Tom Rini
2002-01-29 5:05 ` Kaoru Fukui
2002-01-29 6:26 ` Troy Benjegerdes
2002-01-29 15:01 ` Tom Rini
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=87sn8sybcx.fsf@fadata.bg \
--to=velco@fadata.bg \
--cc=hozer@drgw.net \
--cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).