From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2451 invoked by alias); 4 Jan 2008 04:44:38 -0000 Received: (qmail 2108 invoked by alias); 4 Jan 2008 04:43:34 -0000 Date: Fri, 04 Jan 2008 07:03:00 -0000 Message-ID: <20080104044334.2107.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/32044] [4.3 regression] udivdi3 counterproductive, unwarranted use In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "mark at codesourcery dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2008-01/txt/msg00278.txt.bz2 ------- Comment #39 from mark at codesourcery dot com 2008-01-04 04:43 ------- Subject: Re: [4.3 regression] udivdi3 counterproductive, unwarranted use fche at redhat dot com wrote: >> Downgrading to P4. We seem to have consensus that this is [not] a GCC wrong-code >> bug. > > Yeah, it seems to be a mistaken expectation of -ffreestanding not to > call libgcc. Maybe a new option to that effect would help? I don't think there's a practical, platform-independent way for GCC to avoid calling libgcc. On some platforms, it has to do that for pretty basic operations. I think we just need to accept that the libgcc API is part of what's required by the compiler; you could imagine that it is "as-if" weak definitions of these functions were emitted in every assembly file by the compiler itself. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32044