From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4835 invoked by alias); 31 Dec 2010 20:03:41 -0000 Received: (qmail 4827 invoked by uid 22791); 31 Dec 2010 20:03:41 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 31 Dec 2010 20:03:37 +0000 From: "joseph at codesourcery dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/47119] sh-symbianelf: symbian-base.o won't build X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: joseph at codesourcery dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Fri, 31 Dec 2010 20:03:00 -0000 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: 2010-12/txt/msg03036.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47119 --- Comment #2 from joseph at codesourcery dot com 2010-12-31 20:03:27 UTC --- On Fri, 31 Dec 2010, amylaar at gcc dot gnu.org wrote: > There are a lot more problems with this port. Here is a patch that makes > the port sort-of build when using GCC as the build compiler; it uses the > weak attribute to work around some issues with having different target > hooks depending on the input language. I objected to a previous patch version using the weak attribute and thought that a way was found at that point to do without it. There's no way it should be needed on the host for anything reasonable in GCC - I don't know what this port is trying to do but there's bound to be a better way. Split up objects as necessary and ensure that exactly one implementation of each function needed is linked into each compiler. If the problem is generic functions calling C-family ones, use function pointers initialized at an appropriate point. (REGISTER_TARGET_PRAGMAS is abused by ARM as a "C family initialization hook" though a separate hook would be better.)