From owner-freebsd-toolchain@freebsd.org Fri Jun 23 01:01:33 2017 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65EF8D98A5E for ; Fri, 23 Jun 2017 01:01:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5444271B80 for ; Fri, 23 Jun 2017 01:01:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v5N11XDc039710 for ; Fri, 23 Jun 2017 01:01:33 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-toolchain@FreeBSD.org Subject: [Bug 220184] clang 4.0.0 segfaults on buildworld Date: Fri, 23 Jun 2017 01:01:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-toolchain@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 01:01:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220184 --- Comment #15 from Mark Millard --- (In reply to Mark Millard from comment #14) My paragraph: "If this were a general problem the build servers would not be able to build the releases, ports, and such." was poorly chosen. I should have referred to just test builds that are based on head, stable/11, or the drafts of 11.1 . (I expect that there have been many.) These likely start with projects/clang*-import/ testing and continue with head, stable/11, and the 11.1 drafts. The official of releases and such likely are still based on an older context building the newer context. I do not know if they build and use a bootstrap clang 4 and then use it or not when the target is head, stable/11, or an 11.1 draft version of some kind. It could be that only the system compiler is built and installed but not used for anything relative to buildworld buildkernel activity. As I understand exp-runs were made for building ports that were based on clang 4. This might still be on-going. My own activity is incremental updates of head, so using clang 4 to build a bootstrap compiler that is clang 4 when needed. Then using the resultant clang 4 either way. (I ignore here experimenting with devel/*xtoolchain* or using gcc 4.2.1 where I have to [32-bit powerpc kernel that finishes booting correctly].) There is also likely activity of other people working based on clang 4, including buildworld, buildkernel, and building ports (ports that do not force some gcc or some other toolchain). I expect there is still enough activity based on clang 4 that my overall argument structure still holds: It would be good to try something that matches a well used, well established build configuration overall and see what the status is for that build configuration. I'll note that my activity is mostly based on system-clang, not devel/llvm40 clang. Although I have attempted devel/xtoolchain-llvm40 for buildworld and buildkernel when there were unusual failures like missing routines in linking. (So far system-clang and devel/xtoolchain-llvm40 have matched for such build issues. But I've rarely tried this.) --=20 You are receiving this mail because: You are the assignee for the bug.=