From: Ben Greear <greearb@candelatech.com>
To: "David S. Miller" <davem@redhat.com>
Cc: rddunlap@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: unresolved symbol: __udivdi3
Date: Fri, 19 Apr 2002 16:33:46 -0700 [thread overview]
Message-ID: <3CC0A95A.2070000@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0204191408450.15597-100000@dragon.pdx.osdl.net> <3CC092F2.8090009@candelatech.com> <20020419.145651.82832824.davem@redhat.com>
Also, for what it's worth, do_div on x86 seems to corrupt arguments
given to it, and may do other screwy things. I'm just going to
go back to casting and let user-space do any precise division.
David S. Miller wrote:
> From: Ben Greear <greearb@candelatech.com>
> Date: Fri, 19 Apr 2002 14:58:10 -0700
>
> then I get another unresolved symbol:
> __umodi3
>
> Someone needs to add this routine under arch/sparc/lib/
>
> I'm guessing that there is some optimization the compiler is doing that
> is using the mod operator somehow, but I am unsure about how to work around
> this.
>
> "guessing"? Have a look the definition of do_div in asm-sparc/div64.h
> it explicitly does a mod operation :-)
>
>
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2002-04-19 23:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 21:03 unresolved symbol: __udivdi3 Ben Greear
2002-04-19 21:09 ` Randy.Dunlap
2002-04-19 21:58 ` Ben Greear
2002-04-19 21:56 ` David S. Miller
2002-04-19 22:12 ` Ben Greear
2002-04-19 23:33 ` Ben Greear [this message]
2002-04-19 23:42 ` Randy.Dunlap
2002-04-20 19:02 ` Chris Caputo
2002-04-25 6:15 ` Randy.Dunlap
2002-04-25 7:35 ` swap_free: Bad swap offset entry Robert Schelander
2002-04-25 14:05 ` Hugh Dickins
2002-04-19 21:38 ` unresolved symbol: __udivdi3 Andreas Dilger
2002-04-20 16:25 ` GOTO Masanori
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=3CC0A95A.2070000@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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