All of lore.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: Thomas Schlichter <schlicht@uni-mannheim.de>,
	linux-kernel@vger.kernel.org
Subject: Re: problem using integer division in kernel modules
Date: Tue, 21 Jan 2003 01:26:29 -0800	[thread overview]
Message-ID: <3E2D1245.131E41DB@mvista.com> (raw)
In-Reply-To: 20030115191122.GV27709@mea-ext.zmailer.org

Matti Aarnio wrote:
> 
> On Wed, Jan 15, 2003 at 07:41:29PM +0100, Thomas Schlichter wrote:
> > Hi,
> >
> > I am writing at a small kernel module and have a problem now using / and %. If
> > I do so I get following unresolved symbols when the module should be loaded:
> >   __divdi3
> >   __moddi3
> 
>   64-bit division with non-constant non-power-of-two divider.
> 
> > Could you please help me and tell me what I do wrong..?
> 
>   The kernel is linked without gcc builtin libraries.
>   Reasons can be found from FAQ (see footer), or archives.

You may want to check out .../include/asm-???/div64.h.  It
allows some limited divides with 64-bit numbers.  Look at
several so you understand what it does and does not do.

-g
> 
> /Matti Aarnio
> -
> 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/

-- 
George Anzinger   george@mvista.com
High-res-timers: 
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml

      reply	other threads:[~2003-01-21  9:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 18:41 problem using integer division in kernel modules Thomas Schlichter
2003-01-15 19:11 ` Matti Aarnio
2003-01-21  9:26   ` george anzinger [this message]

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=3E2D1245.131E41DB@mvista.com \
    --to=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.aarnio@zmailer.org \
    --cc=schlicht@uni-mannheim.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.