kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: bernd@petrovitsch.priv.at (Bernd Petrovitsch)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Doubt regarding __udivdi3
Date: Wed, 05 Jan 2011 15:45:03 +0100	[thread overview]
Message-ID: <1294238703.28520.0.camel@thorin> (raw)
In-Reply-To: <AANLkTinpmYwGGcTc3FJ+ae1_LM7n6zYDZtAiZyZo5825@mail.gmail.com>

On Mit, 2011-01-05 at 19:21 +0530, Ponmuthu Subramaniam Nandan wrote:
> Hi Gaurav,
> 
>         I'm trying to insert a module into the kernel (2.6.35.5).
>         There are no
>         errors during the "make" phase. There are only warnings
>         regarding two
>         symbols :
>         WARNING: "__udivdi3"
>         [/media/Study/project_work/splitting_merging/radc_try1/radc1.ko]
>         undefined!
>         WARNING: "__umoddi3"
>         [/media/Study/project_work/splitting_merging/radc_try1/radc1.ko]
>         undefined!
>         
> The symbol __udivdi3 & __umoddi3 are compiler generated functions
> calls for specific 
> Arithmetic function in your code (In this case its division). The
> definitions of that function 
> (for the specific ARCH your are building for) would be in the
> respective libraries (libgcc). 

The first hit on google is
http://stackoverflow.com/questions/1063585/udivdi3-undefined-howto-find-code.

That should explain it. 
Bernd
-- 
Bernd Petrovitsch                  Email : bernd at petrovitsch.priv.at
                     LUGA : http://www.luga.at

      reply	other threads:[~2011-01-05 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05 12:06 Doubt regarding __udivdi3 Gaurav Mahajan
2011-01-05 12:41 ` Asutosh Das
2011-01-05 13:51 ` Ponmuthu Subramaniam Nandan
2011-01-05 14:45   ` Bernd Petrovitsch [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=1294238703.28520.0.camel@thorin \
    --to=bernd@petrovitsch.priv.at \
    --cc=kernelnewbies@lists.kernelnewbies.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).