From owner-freebsd-ppc@freebsd.org  Sun Mar  6 01:13:29 2016
Return-Path: <owner-freebsd-ppc@freebsd.org>
Delivered-To: freebsd-ppc@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 EF9469DB98E
 for <freebsd-ppc@mailman.ysv.freebsd.org>;
 Sun,  6 Mar 2016 01:13:29 +0000 (UTC)
 (envelope-from markmi@dsl-only.net)
Received: from asp.reflexion.net (outbound-mail-210-1.reflexion.net
 [208.70.210.1])
 (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 8BEC17F5
 for <freebsd-ppc@freebsd.org>; Sun,  6 Mar 2016 01:13:29 +0000 (UTC)
 (envelope-from markmi@dsl-only.net)
Received: (qmail 31153 invoked from network); 6 Mar 2016 01:13:20 -0000
Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1)
 by 0 (rfx-qmail) with SMTP; 6 Mar 2016 01:13:20 -0000
Received: by mail-cs-01.app.dca.reflexion.local
 (Reflexion email security v7.80.0) with SMTP;
 Sat, 05 Mar 2016 20:13:37 -0500 (EST)
Received: (qmail 12143 invoked from network); 6 Mar 2016 01:13:37 -0000
Received: from unknown (HELO iron2.pdx.net) (69.64.224.71)
 by 0 (rfx-qmail) with SMTP; 6 Mar 2016 01:13:37 -0000
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net
 [76.115.7.162])
 by iron2.pdx.net (Postfix) with ESMTPSA id 2656A1C43D7;
 Sat,  5 Mar 2016 17:13:17 -0800 (PST)
From: Mark Millard <markmi@dsl-only.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: 207732 submitted: libgcc_s .eh_frame handling messes up interpreting
 powerpc/powerpc64 frame pointer register use produced by clang 3.8.0
Message-Id: <7BC7F7FF-FF5C-4BE9-875C-6997BC194295@dsl-only.net>
Date: Sat, 5 Mar 2016 17:13:21 -0800
To: Roman Divacky <rdivacky@vlakno.cz>,
 FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>,
 FreeBSD Toolchain <freebsd-toolchain@freebsd.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
X-BeenThere: freebsd-ppc@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Porting FreeBSD to the PowerPC <freebsd-ppc.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ppc>,
 <mailto:freebsd-ppc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ppc/>
List-Post: <mailto:freebsd-ppc@freebsd.org>
List-Help: <mailto:freebsd-ppc-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ppc>,
 <mailto:freebsd-ppc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Mar 2016 01:13:30 -0000

I have submitted FreeBSD bug 207732:

libgcc_s .eh_frame handling messes up interpreting powerpc/powerpc64 =
frame pointer register use produced by clang 3.8.0

In essence clang++ 3.8.0 generates Frame Pointer Register based code =
(r31 in addition to the r1 stack pointer) that g++ 4.2.1/4.9/5.3 =
(normally) do not and so the clang++ 3.8.0 code ends up touching an =
error in libgcc_s interpreting .eh_frame information for C++ exception =
handling that gcc 4.2.1 and the like side step by not using such a Frame =
Pointer register.

Note: The context for libgcc_s was a clang 3.8.0 based buildworld. A gcc =
buildworld does not involve such a Frame Pointer Register.

I do not know if any TARGET_ARCH's other than powerpc/powerpc64 also =
generate such Frame Pointer Register like code and so might touch the =
same error.


=3D=3D=3D
Mark Millard
markmi at dsl-only.net