All of lore.kernel.org
 help / color / mirror / Atom feed
From: "" <simon@baydel.com>
To: Tim Schmielau <tim@physik3.uni-rostock.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: unresolved symbols __udivdi3 and __umoddi3
Date: Mon, 28 Jan 2002 04:21:31 -0000	[thread overview]
Message-ID: <3C54D1CB.23664.50D4C3@localhost> (raw)
In-Reply-To: <Pine.LNX.3.95.1020125114634.762A-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.4.33.0201252234530.18494-100000@gans.physik3.uni-rostock.de>

First of all I would like to thank all the people that responded to my 
mail. Unfortunately the numbers I am using are not restricted to 
powers of two so I could not simply shift the data. I have decided to 
use the div64.h solution and it seems to work well. 

I have looked at this header file and I do not understand the asm 
syntax. 

In particular the only x86 div instruction I know only returns a 32 bit 
div result. Because I don't understand the div64 header I cannot 
see how a 64 bit result is calculated.

I also tried this header in a regular application. This failed to return 
the modulus although it works in a module.

Is this asm syntax documented anywhere ? 

Thanks Again 

Simon.


On 25 Jan 2002, at 22:42, Tim Schmielau wrote:

> On Fri, 25 Jan 2002, Richard B. Johnson wrote:
> 
> > On Fri, 25 Jan 2002,  wrote:
> >
> > > I am writing a module and would like to perform arithmetic on long
> > > long variables. When I try to do this the module does not load due
> > > to the unresolved symbols __udivdi3 and __umoddi3. I notice these
> > > are normally defined in libc. Is there any way I can do this in a
> > > kernel module.
> > >
> > > Many Thanks
> > >
> > > Simon.
> >
> > Normally, in modules, the granularity is such that divisions can
> > be made by powers-of-two. In a 32-bit world, the modulus that you
> > obtain with umoddi3 (the remainder from a long-long, division) should
> > normally fit within a 32-bit variable. If you insist upon doing 64-bit
> > math in a 32-bit world, then you can either make your own procedures
> > and link them, of you can "appropriate" them from the 'C' runtime
> > library code, include them with your source, assemble, and link them
> > in.
> 
> If 64-bit arithmetics cannot be avoided, the do_div64() macro defined in
> include/asm/div64.h comes in handy.
>   mod = do_div((unsigned long) x, (long) y)
> will set  x  to the quotient x/y  and  mod  to the remainder  x%y .
> 
> Tim
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


__________________________

Simon Haynes - Baydel 
Phone : 44 (0) 1372 378811
Email : simon@baydel.com
__________________________

  reply	other threads:[~2002-01-28 15:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25  6:31 unresolved symbols __udivdi3 and __umoddi3 simon
2002-01-25 16:45 ` Andreas Dilger
2002-01-25 16:56 ` Richard B. Johnson
2002-01-25 21:42   ` Tim Schmielau
2002-01-28  4:21     ` simon [this message]
2002-01-28 17:38       ` Tim Schmielau
2002-01-28 19:17       ` Daniel Phillips
2002-01-28 19:28         ` Mark Zealey
2002-01-28 19:46         ` Momchil Velikov
2002-01-28 20:06           ` Daniel Phillips
2002-01-28 20:14             ` Momchil Velikov
2002-01-29 16:38             ` Horst von Brand
2002-01-30  8:09               ` Daniel Phillips
2002-01-30  8:43                 ` Jeff Garzik
2002-01-30  8:23               ` Jeff Garzik
2002-01-28 11:08   ` Daniel Phillips
2002-01-28 11:10     ` Arjan van de Ven
2002-01-28 11:47       ` Daniel Phillips
2002-01-25 17:06 ` christophe barbé
2002-01-25 18:53   ` Christoph Hellwig
2002-01-25 19:03     ` christophe barbé

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=3C54D1CB.23664.50D4C3@localhost \
    --to=simon@baydel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim@physik3.uni-rostock.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.