------- Comment #22 from rguenther at suse dot de 2007-11-09 16:33 ------- Subject: Re: [4.3 regression] udivdi3 counterproductive, unwarranted use
On Fri, 9 Nov 2007, bunk at stusta dot de wrote: > ------- Comment #21 from bunk at stusta dot de 2007-11-09 16:26 ------- > Let's leave the right/wrong discussion and look at it more pragmatically: > > Could gcc get some kind of --expensive-libgcc flag that tells gcc that libgcc > calls are a bit more expensive than usually and should be avoided? While this is technically possible we already face stability and maintainability problems in other areas where we do so (for example the conditionally available C99 math has in the past lead to many internal compiler errors). So I would prefer not to go this route. Which does _not_ mean that we absolutely will not fix this issue and try to avoid creating final value replacement that involves a division/modulus. But as there exist multiple work-arounds for this issue, a nice and complete solution is certainly not very high priority. Richard. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32044
