From: "David S. Miller" <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: div, udiv, mul, umul, rem, urem broken again?!?
Date: Sun, 06 Nov 2005 20:58:48 +0000 [thread overview]
Message-ID: <20051106.125848.29593875.davem@davemloft.net> (raw)
In-Reply-To: <1128550254.2140.103.camel@localhost.localdomain>
From: Rusty Russell <rusty@rustcorp.com.au>
Date: Sun, 06 Nov 2005 17:27:20 +1100
> Argh, it would need to use the alias trick, yes. As I said, untested.
> But, looking in 2.6.12, sparc already did this aliasing?
And that aliasing trick is what we were trying to get rid
of. It's nearly impossible to get it to work on all versions
of the compiler at once.
I thought you had proposed a way to do it without aliases :-)
> So my question is (I missed the beginning of this thread), why do you
> want to avoid the simple "omit the . at the front" name mangling scheme
> which modpost, kernel/module.c and module-init-tools already understand,
> and use a different mangling scheme? Name clash with something else?
> Why is "_Udiv" a better name than "udiv"?
Good question, I'll think about this some more.
next prev parent reply other threads:[~2005-11-06 20:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 22:10 div, udiv, mul, umul, rem, urem broken again?!? Tom 'spot' Callaway
2005-10-05 22:17 ` Tom 'spot' Callaway
2005-10-06 0:24 ` David S. Miller
2005-10-06 13:21 ` Tom 'spot' Callaway
2005-10-10 10:20 ` Rusty Russell
2005-10-10 14:35 ` Tom 'spot' Callaway
2005-10-10 18:22 ` David S. Miller
2005-10-11 10:03 ` Rusty Russell
2005-11-06 0:40 ` David S. Miller
2005-11-06 4:13 ` Tom 'spot' Callaway
2005-11-06 6:27 ` Rusty Russell
2005-11-06 20:56 ` David S. Miller
2005-11-06 20:58 ` David S. Miller [this message]
2006-02-08 20:25 ` Martin Habets
2006-02-08 20:51 ` Tom 'spot' Callaway
2006-02-08 20:56 ` Al Viro
2006-02-09 1:29 ` Rusty Russell
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=20051106.125848.29593875.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=sparclinux@vger.kernel.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 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.