From owner-freebsd-ports@FreeBSD.ORG Fri Mar 18 10:40:42 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E526D106564A for ; Fri, 18 Mar 2011 10:40:42 +0000 (UTC) (envelope-from marcov@stack.nl) Received: from mx1.stack.nl (relay02.stack.nl [IPv6:2001:610:1108:5010::104]) by mx1.freebsd.org (Postfix) with ESMTP id 873EC8FC20 for ; Fri, 18 Mar 2011 10:40:42 +0000 (UTC) Received: from turtle.stack.nl (turtle.stack.nl [IPv6:2001:610:1108:5010::132]) by mx1.stack.nl (Postfix) with ESMTP id 62C893592F8 for ; Fri, 18 Mar 2011 11:40:38 +0100 (CET) Received: by turtle.stack.nl (Postfix, from userid 816) id 4DB6C1737B; Fri, 18 Mar 2011 11:40:38 +0100 (CET) In-Reply-To: <4D8244A4.2090206@FreeBSD.org> To: freebsd-ports@FreeBSD.org Date: Fri, 18 Mar 2011 11:40:38 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL124d (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" Message-Id: <20110318104038.4DB6C1737B@turtle.stack.nl> From: marcov@stack.nl (Marco van de Voort) Cc: Subject: Re: Compiling ports in a post-9.0-RELEASE world X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2011 10:40:43 -0000 In our previous episode, Matthias Andree said: > > So far I've found clang surprisingly good in that it revealed a few > quirks in my own software (in C) that GCC or ICC had silently accepted, > and the static analyzer has a few rough edges, but I have found bugs in > my own software, not in clang 2.8 so far, although I suspect that a few > might linger there. How much changes for non-(GC)C ports? In other words, ports that directly use AS and LD to generate binaries, but might also link to C libraries outside of gcc's control. (I'm thinking about e.g. lang/fpc here) Issues like - Are there fundamental startup code (CSU) changes due to this in 9? - libraries that might need to be implicitely linked when linking against C code (like libgcc,c) - Do certain libc internal macros change (like __errno_location) - Do lowlevel details of stuff like TLS change? Of course I'll load up some RC or DP in a VM if necessary to find my own answers. But if somebody knows some details, it would help guestimating the effort.