From owner-freebsd-toolchain@freebsd.org  Fri Jan  6 22:49:33 2017
Return-Path: <owner-freebsd-toolchain@freebsd.org>
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 854EBCA2305
 for <freebsd-toolchain@mailman.ysv.freebsd.org>;
 Fri,  6 Jan 2017 22:49: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 7450B1210
 for <freebsd-toolchain@FreeBSD.org>; Fri,  6 Jan 2017 22:49: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 v06MnXE0056516
 for <freebsd-toolchain@FreeBSD.org>; Fri, 6 Jan 2017 22:49:33 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-toolchain@FreeBSD.org
Subject: [Bug 215819] head r311147's clang 3.9.1 for powerpc64: locore.o
 generation messed up: generates R_PPC64_ADDR16_DS instead of R_PPC64_TOC16_DS
 with .toc
Date: Fri, 06 Jan 2017 22:49:33 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: CURRENT
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: freebsd-toolchain@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-215819-29464-IqabzRePBd@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-215819-29464@https.bugs.freebsd.org/bugzilla/>
References: <bug-215819-29464@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-toolchain@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Maintenance of FreeBSD's integrated toolchain
 <freebsd-toolchain.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-toolchain/>
List-Post: <mailto:freebsd-toolchain@freebsd.org>
List-Help: <mailto:freebsd-toolchain-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jan 2017 22:49:33 -0000

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

--- Comment #2 from Mark Millard <markmi@dsl-only.net> ---
(In reply to Mark Linimon from comment #1)

-r311147 is just the version I tested. It does not
show how long the problem has existed.

Usually folks want to know if the current (or a recent)
build still has a problem before going further. Plus
it is more time and effort to back trace to the first
example.

In this case it is likely clang 3.9.0 and 3.9.1's whole
powerpc64 history in FreeBSD: effectively I've just
learned more about "already known to be broken" details
and reported them. There was prior list activity about
the bad register offsets such as 0(r2) but without the
R_PPC64_ADDR16_DS vs. R_PPC64_TOC16_DS information.

--=20
You are receiving this mail because:
You are the assignee for the bug.=