I don't have a massive amount expertise in this area but I'll look into it.
>From what I can tell this seems to only affect powerpc64.

Bill

On Tue, Sep 20, 2016 at 4:55 PM, Mark Millard <mar...@dsl-only.net> wrote:

>
> 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?
> >
> > -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=1 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:
> >>
> >> The below forward from freebsd-pcc's list confirms that binutils 2.27
> not working for powerpc64 (& powerpc?) contexts.
> >>
> >> 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.
> >>
> >> ===
> >> Mark Millard
> >> markmi at dsl-only.net
> >>
> >> On 2016-Sep-20, at 11:19 AM, Krzysztof Parzyszek <kristof at
> swissmail.org> wrote:
> >>
> >>> I've had similar problems after building gcc-4.8.  After reverting
> back to binutils 2.25 and rebuilding, it worked fine.
> >>>
> >>> -Krzysztof
> >>>
> >>> 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?
> >>>>
> >>>> Thanks,
> >>>> Bill
>
>
> ===
> Mark Millard
> markmi at dsl-only.net
>
> _______________________________________________
> freebsd-toolch...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
> To unsubscribe, send any mail to "freebsd-toolchain-
> unsubscr...@freebsd.org"
>
_______________________________________________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Reply via email to