From owner-freebsd-toolchain@FreeBSD.ORG Mon Nov 18 21:20:03 2013 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mandree.no-ip.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A1890D37 for ; Mon, 18 Nov 2013 21:20:03 +0000 (UTC) Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 133F623CE7C for ; Mon, 18 Nov 2013 22:20:02 +0100 (CET) Message-ID: <528A8481.9010200@FreeBSD.org> Date: Mon, 18 Nov 2013 22:20:01 +0100 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: freebsd-toolchain@freebsd.org Subject: clang++ 3.3 issue (excessively slow compile vs. gcc 4.6 in just one file of a port) X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Nov 2013 21:20:03 -0000 [Please keep me in Cc:, I am not subscribed.] Greetings, I have recently spent some efforts getting rawtherapee to compile on 10-stable. I think I succeeded, and came across something I find worth investigating. For just one of rawtherapee's files, clang++ 3.3's compile time is excessively long, compared both to the other files, as well as against gcc 4.6. System: FreeBSD 10.0-BETA3 #1 r258178: Fri Nov 15 20:00:11 CET 2013 toor@vmf10:/usr/obj/usr/src/sys/GENERIC Compiler: FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 Target: x86_64-unknown-freebsd10.0 Thread model: posix The port as it currently stands hacks the cmake-generated build.make to compile ipsharpen.cc with only -O1 option. If I remove that patch, so that the port compiles with -O2 or -O3, compiling that single file takes too long for me to wait for it, in excess of 10 minutes, on my 2.5 GHz AMD Phenom II X4. GCC 4.6 does not exhibit such behaviour. I have not yet isolated what might cause this, how would I best go about that so we can pin this issue and possibly fix clang++? Thanks. Best regards Matthias