Date: Mon, 02 Jan 2017 20:25:13 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 215600] devel/powerpc64-gcc based buildkernel: sys/powerpc/powerpc/db_trace.c rejected for: '__builtin_frame_address' with a nonzero argument is unsafe Message-ID: <bug-215600-8-TMsygMJqWO@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-215600-8@https.bugs.freebsd.org/bugzilla/> References: <bug-215600-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215600 --- Comment #2 from Mark Millard <markmi@dsl-only.net> --- [Just recording John Baldwin's note about the issue in bugzilla.] In: https://lists.freebsd.org/pipermail/freebsd-toolchain/2017-January/002542.h= tml John Baldwin wrote the following: From: John Baldwin . . . . . . Date: January 2, 2017 at 8:07:57 AM PST . . . Try using '0' instead of '1'. You might get an extra frame in the backtrace compared to before. A simple way to test is to add 'options KDB_TRACE' and then trigger a panic (e.g. sysctl debug.kdb.panic=3D1) Side note by Mark Millard: I've no clue if this is the direction that the powerpc64 (and powerpc) FreeBSD folks want to go/investigate for the compiler's report or not. As stands I'm using WERROR=3D to allow the buildkernel to complete. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215600-8-TMsygMJqWO>