Date: Mon, 31 Oct 2016 04:43:03 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 213785] stable/11 -r307797 on BPi-M3 (cortex-a7): xgcc's cc1 during lang/gcc6 build gets SIGSYS failures (/usr/ports -r424540) Message-ID: <bug-213785-7-fEmETLJnWJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-213785-7@https.bugs.freebsd.org/bugzilla/> References: <bug-213785-7@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213785 Mark Millard <markmi@dsl-only.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Overcome By Events Status|New |Closed --- Comment #8 from Mark Millard <markmi@dsl-only.net> --- (In reply to Mark Millard from comment #7) I've tracked down a problem with the armv6/cortex-a7 code generated in lang/gcc6's xgcc' cc1 and submitted bugzilla 213934 against lang/gcc6 for it. The history here in bugzilla 213785 is not of much use for the lang/gcc6 issue. (It might be somewhat useful for the truss crash issue that xgcc's cc1 exposed.) So I'm closing this report so that lang/gcc6 has a simpler report with just the actual code generation problem documented. But bugzilla 213778's report for truss's crashing when watching the failing cc1 is still active and John Baldwin has taken at least one stab at fixing that issue. So for now I leave the BPI-M3 environment in the form that allows me to test truss updates: I'm not exploring compiler option variations and such for lang/gcc6. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-213785-7-fEmETLJnWJ>