------- Comment #35 from mark at codesourcery dot com 2007-11-27 19:45 ------- Subject: Re: [4.3 regression] udivdi3 counterproductive, unwarranted use
bunk at stusta dot de wrote: > Even if this specific issue in the kernel would turn out as a misoptimization, > the general problem would still remain waiting to pop up at some later time at > a different place. Indeed. However, I think that the kernel developers should be aware that GCC is not designed to avoid libgcc functions. GCC fundamentally assumes that it may call various functions from libgcc as it pleases. (Sometimes it may do so for good reasons, sometimes it may be that it does it suboptimally.) Because there's nothing in GCC to keep it from "randomly" calling libgcc functions, if the kernel wants to be robust against different versions of GCC, it should provide definitions of these functions. There's no easy way to make GCC avoid these functions. That's not meant to defend GCC calling this particular function in this particular circumstance, of course. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32044
