From owner-freebsd-ports-bugs@freebsd.org  Mon Mar 27 20:13:28 2017
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
Delivered-To: freebsd-ports-bugs@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 3B5B7D20494
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Mon, 27 Mar 2017 20:13:28 +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 2AC8FE62
 for <freebsd-ports-bugs@FreeBSD.org>; Mon, 27 Mar 2017 20:13:28 +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 v2RKDSxt023141
 for <freebsd-ports-bugs@FreeBSD.org>; Mon, 27 Mar 2017 20:13:28 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 218125] compiler:c++11-lib feature should choose gcc5+ or
 clang3x for powerpc64
Date: Mon, 27 Mar 2017 20:13:28 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Ports Framework
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
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: portmgr@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-218125-13-H68juvaapC@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-218125-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-218125-13@https.bugs.freebsd.org/bugzilla/>
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-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Mar 2017 20:13:28 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218125

Mark Millard <markmi@dsl-only.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |markmi@dsl-only.net

--- Comment #1 from Mark Millard <markmi@dsl-only.net> ---
clang (even 4.0) does not work for TARGET_ARCH=3Dpowerpc :
It has basic problems with stack handling for R30 use
when floating point is involved for the ABI that FreeBSD
uses. Also  the handing of thrown C++ exceptions is
messed up.

clang (even 4.0) does not work for TARGET_ARCH-powrepc64 :
The handling of thrown C++ exceptions is messed up.

There are llvm bugzilla submittals for such things and
they are on the llvm bugzilla meta- entry for what blocks
use by FreeBSD as the system compiler.

Note: clang 3.x was in worse shape until 3.9.x .

clang is a long way from being able to be the compiler
for the likes of kyua for QA testing FreeBSD.

So I believe that any "or clang" is a bad idea still.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=