All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] ARM missing __udivdi3 in lib_arm or fix 64bit division in nand_util.c?
Date: Tue, 31 Jul 2007 07:38:19 +0200	[thread overview]
Message-ID: <46AECACB.2020003@googlemail.com> (raw)


On ARM (don't know for other architectures ;) ) compiling and linking 
nand_util.c results on recent git in

~/uboot/drivers/nand/nand_util.c:657: undefined reference to `__udivdi3'
drivers/nand/libnand.a(nand_util.o): In function `nand_write_opts':
~/uboot/drivers/nand/nand_util.c:481: undefined reference to `__udivdi3'
drivers/nand/libnand.a(nand_util.o): In function `nand_erase_opts':
~/uboot/drivers/nand/nand_util.c:214: undefined reference to `__udivdi3'

In lib_arm __udivsi3 and friends are available, but __udivdi3 is 
missing. There is a fix by modifying nand_util.c

http://sourceforge.net/mailarchive/forum.php?thread_name=468D2650.10603%40rfo.atmel.com&forum_name=u-boot-users

to not do any 64bit divisions any more. Now, I wonder what is the 
correct fix for this? Should lib_arm provide __udivdi3 as well or 
should nand_util.c be fixed as in above link to avoid 64bit divisions?

Best regards

Dirk

             reply	other threads:[~2007-07-31  5:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31  5:38 Dirk Behme [this message]
2007-07-31  8:17 ` [U-Boot-Users] ARM missing __udivdi3 in lib_arm or fix 64bit division in nand_util.c? Håvard Skinnemoen
2007-07-31 19:26   ` Dirk Behme
2007-07-31 20:27     ` Wolfgang Denk
2007-08-01 17:55       ` Dirk Behme
2007-08-01 20:14         ` Wolfgang Denk
2007-08-01 20:15         ` Wolfgang Denk

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=46AECACB.2020003@googlemail.com \
    --to=dirk.behme@googlemail.com \
    --cc=u-boot@lists.denx.de \
    /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.