Date: Tue, 20 Sep 2016 14:55:35 -0700 From: Mark Millard <markmi@dsl-only.net> To: Dimitry Andric <dim@FreeBSD.org> Cc: FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: binutils 2.27 [not working for powerpc64 (and powerpc?)] Message-ID: <05960430-8B1B-4B84-AC28-019BFD031021@dsl-only.net> In-Reply-To: <7386974C-F100-41DF-B742-28C1DB4E5F07@FreeBSD.org> References: <CACcTwYkNvKTBr6D8gek7%2Bgkg_fWet-cdutLfWtx1RoSQTxQYPw@mail.gmail.com> <cf0f3b64-6530-449c-a3e6-1c3acebabc88@swissmail.org> <9972E75F-9102-4A18-BA9B-33AB6BF64789@dsl-only.net> <7386974C-F100-41DF-B742-28C1DB4E5F07@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-Sep-20, at 1:59 PM, Dimitry Andric <dim at FreeBSD.org> wrote: > Has anyone succeeded in bisecting upstream binutils, to see where this = problem was introduced? >=20 > -Dimitry Apparently not from what I've seen in the lists. It will be a couple/few = weeks before I again have powerpc64 or powerpc access. I've just been = monitoring powerpc64 & powerpc things in hopes of things working once I = have access again --or at least my knowing what to do to sidestep issues = and what sequence to progress in from what I had in very early 2016-June = when I lost access temporarily. May be someone will have the time & knowledge to bisect the upstream = binutils materials. I may figure how to sometime after I get access = again. But it is not the only FreeBSD powerpc64 (PowerMac) thing that = I'd likely be investigating. (Example: because of problems with = sprg0-value handling for FreeBSD vs. OpenFirmware on PowerMac = powerpc64's: testing usefdt=3D1 mode for Nathan Whitehorn in hopes of = future changes avoiding OpenFirmware use from FreeBSD. Nathan put the = hooks in place for testing somewhat after I'd already lost access.) I wonder if the various(?) binutil port(s) that are 2.27 based now and = can be built to target powerpc64/powerpc should be marked broken for = powerpc64/powerpc until this is figured out. Any ports that are only for = targeting powerpc64 or powerpc probably should not be at 2.27 at this = point. I've submited a bugzilla report 212868 for devel/binutils with the text = of the list reports that I've quoted. > On 20 Sep 2016, at 22:56, Mark Millard <markmi at dsl-only.net> wrote: >>=20 >> The below forward from freebsd-pcc's list confirms that binutils 2.27 = not working for powerpc64 (& powerpc?) contexts. >>=20 >> Note: Krzysztof Parzyszek is one of the two people that have recently = been working on updating clang/llvm for fixing some of the issues that = block FreeBSD from using clang for powerpc and powerpc64 for buildworld = and buildkernel. >>=20 >> =3D=3D=3D >> Mark Millard >> markmi at dsl-only.net >>=20 >> On 2016-Sep-20, at 11:19 AM, Krzysztof Parzyszek <kristof at = swissmail.org> wrote: >>=20 >>> I've had similar problems after building gcc-4.8. After reverting = back to binutils 2.25 and rebuilding, it worked fine. >>>=20 >>> -Krzysztof >>>=20 >>> On 9/9/2016 11:32 AM, Bill Sorenson wrote: >>>> Everything I've built with the new binutils using either GCC 4.9, = 5.4 or >>>> 6.2 instantly dumps when run. This is on an Xserve G5. Is this just = me or >>>> is there something genuinely broken here? >>>>=20 >>>> Thanks, >>>> Bill =3D=3D=3D Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?05960430-8B1B-4B84-AC28-019BFD031021>