> > Why 64-bit divides in particular were victimised in this manner is a
> > matter for speculation ;)
>
> Because gcc historically _cannot_ generate an efficient 64/32->64
> divide. It ends up doing a full 64/64 divide thing.
You're right here. I've been too quick in putting my faith in gcc ;-)
Shouldn't we complain to the gcc people? The 64/32 division is a
rather common operation in many applications besides the kernel, so
you'd expect gcc to get it right without polluting every single
project with reimplementations of do_div().
-- // Bernardo Innocenti - Develer S.r.l., R&D dept. \X/ http://www.develer.com/Please don't send Word attachments - http://www.gnu.org/philosophy/no-word-attachments.html
- 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/