From: Bart Van Assche <bart.vanassche@gmail•com>
To: Joe Eykholt <jeykholt@cisco•com>
Cc: Randy Dunlap <randy.dunlap@oracle•com>,
"Sachin P. Sant" <sachinp@in•ibm.com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
linux-scsi <linux-scsi@vger•kernel.org>
Subject: Re: next Feb 13 drivers/scsi/aha1542.ko build break
Date: Fri, 13 Feb 2009 20:35:55 +0100 [thread overview]
Message-ID: <e2e108260902131135g515d219cpacecdc2ae0e10bb7@mail.gmail.com> (raw)
In-Reply-To: <4995C66E.1000800@cisco.com>
(resending as plain text)
On Fri, Feb 13, 2009 at 8:13 PM, Joe Eykholt <jeykholt@cisco•com> wrote:
> The kernel infrastructure should fix that without requiring the driver to change.
> Drivers ought to be allowed to divide.
>
> I've also seen this in another driver that divided a u64 by a constant.
> I noticed that linux/math64.h provides div_u64(), but it seems awkward to call
> that when the compiler generates a call to __udivdi3 (apparently).
>
> Can't we just provide __udivdi3, since gcc generates that call?
> Otherwise, problems like this will continue to crop up.
A complete list of integer functions to which gcc generates calls can
be found here:
http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gccint/Integer-library-routines.html
Some links to past discussions about this subject:
* http://lkml.org/lkml/2003/7/2/5
* http://lkml.org/lkml/2004/9/23/376
Bart.
next prev parent reply other threads:[~2009-02-13 19:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 6:55 linux-next: Tree for February 13 Stephen Rothwell
2009-02-13 10:03 ` [S390] next Feb13 build break appldata/built-in.o Sachin P. Sant
2009-02-13 11:28 ` [Patch] [S390] Fix appldata build break with !NET Sachin P. Sant
2009-02-13 13:43 ` Heiko Carstens
2009-02-13 11:44 ` next Feb 13 drivers/scsi/aha1542.ko build break Sachin P. Sant
2009-02-13 18:22 ` Randy Dunlap
2009-02-13 18:52 ` James Bottomley
2009-02-13 20:03 ` Ingo Molnar
2009-02-13 19:13 ` Joe Eykholt
2009-02-13 19:34 ` Al Viro
2009-02-13 19:35 ` Bart Van Assche [this message]
2009-02-13 19:22 ` [PATCH -next] usb: fix ehci printk formats Randy Dunlap
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=e2e108260902131135g515d219cpacecdc2ae0e10bb7@mail.gmail.com \
--to=bart.vanassche@gmail$(echo .)com \
--cc=jeykholt@cisco$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-scsi@vger$(echo .)kernel.org \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=sachinp@in$(echo .)ibm.com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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