From owner-freebsd-toolchain@freebsd.org Fri Jul 13 12:30:22 2018 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A30E103A935 for ; Fri, 13 Jul 2018 12:30:22 +0000 (UTC) (envelope-from jonathan@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D88CD83B16 for ; Fri, 13 Jul 2018 12:30:21 +0000 (UTC) (envelope-from jonathan@FreeBSD.org) Received: from [134.153.3.180] (jacob.engr.mun.ca [134.153.27.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: jonathan/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 97F34F1DB for ; Fri, 13 Jul 2018 12:30:21 +0000 (UTC) (envelope-from jonathan@FreeBSD.org) From: "Jonathan Anderson" To: freebsd-toolchain@freebsd.org Subject: Clang 6.0.[01]: UNREACHABLE executed Date: Fri, 13 Jul 2018 10:00:19 -0230 X-Mailer: MailMate (1.11.3r5509) Message-ID: <95573ED5-49CD-4BC6-863D-849C1CAA774D@FreeBSD.org> MIME-Version: 1.0 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.27 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, 13 Jul 2018 12:30:22 -0000 Hi all, I recently ran into an unreachable statement execution in Clang 6, both with v6.0.0 from the llvm60 package and v6.0.1 from HEAD (FreeBSD r335799 / LLVM r335540). I don't see this issue in Clang 5 or in the version that ships with macOS High Sierra (which they're calling 9.1.0, but that's apparently more of a "marketing version" than a true version number). creduce managed to shrink my 2.8 MiB preprocessed sources down to a 604 B test case: https://gist.github.com/trombonehero/2da555bd1292be973f9d14c843c56ae5 This isn't a valid C++ file (e.g., it cuts off after `return o` on line 23), but I would expect it to cause compiler errors rather than a compiler crash. You can see the output from the crash at: https://gist.github.com/trombonehero/8fce4a8f39ae121a2f9f14b45b0b65a1 Any thoughts? Jonathan Anderson -- jonathan@FreeBSD.org