Date: Tue, 21 May 2019 10:22:15 -0300 From: luporl <luporl@freebsd.org> To: Ian Lepore <ian@freebsd.org> Cc: Enji Cooper <yaneurabeya@gmail.com>, Justin Hibbits <jhibbits@freebsd.org>, Li-Wen Hsu <lwhsu@freebsd.org>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: ci.freebsd.org: powerpcspe build failing due to linker error in assembly code Message-ID: <CAC7XEcLDHoCMfBGQ4ek0UExp%2Bw75OzkQEeo_tWVt6wTxbqJNFw@mail.gmail.com> In-Reply-To: <591e35a8be29738fd380c4535d2d13024e7138f9.camel@freebsd.org> References: <839E4F29-0AAC-41C4-A76B-BD218BD8ECBC@gmail.com> <591e35a8be29738fd380c4535d2d13024e7138f9.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
It seems the break was caused by this part of the change:
Index: stand/powerpc/kboot/Makefile
===================================================================
--- stand/powerpc/kboot/Makefile (revision 348004)
+++ stand/powerpc/kboot/Makefile (revision 348005)
@@ -36,9 +36,6 @@
LDFLAGS= -nostdlib -static -T ${.CURDIR}/ldscript.powerpc
-# 64-bit bridge extensions
-CFLAGS+= -Wa,-mppc64bridge
-
DPADD= ${LDR_INTERP} ${LIBOFW} ${LIBFDT} ${LIBSA}
LDADD= ${LDR_INTERP} ${LIBOFW} ${LIBFDT} ${LIBSA}
The integrated assembler of clang doesn't support the -mppc64bridge option,
that is why it was removed.
Fortunately, Justin noticed that kboot is only made for powerpc64 systems
and fixed this in r348028.
Cheers,
-Leandro
On Mon, May 20, 2019 at 10:00 PM Ian Lepore <ian@freebsd.org> wrote:
> On Mon, 2019-05-20 at 17:54 -0700, Enji Cooper wrote:
> > Hi,
> > The following build issue has been cropping up over the past 6
> hours. From
> https://ci.freebsd.org/job/FreeBSD-head-powerpcspe-build/11154/console :
> >
> > 12:49:01 /usr/src/stand/powerpc/kboot/kerneltramp.S: Assembler messages:
> > 12:49:01 /usr/src/stand/powerpc/kboot/kerneltramp.S:88: Error:
> Unrecognized opcode: `rldicr'
> > 12:49:01 /usr/src/stand/powerpc/kboot/kerneltramp.S:96: Error:
> Unrecognized opcode: `rfid'
> >
> > This code hasn’t changed for some time. I’m not sure what
> > triggered the issue, but I suspect it has to deal with an external
> > [toolchain] change.
> > Cheers!
> > -Enji
>
>
> r347992 seems like a good candidate.
>
> -- Ian
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAC7XEcLDHoCMfBGQ4ek0UExp%2Bw75OzkQEeo_tWVt6wTxbqJNFw>