This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/64999] s390x libgo test failure in TestMemoryProfiler
- From: "boger at us dot ibm.com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 24 Feb 2015 22:41:18 +0000
- Subject: [Bug go/64999] s390x libgo test failure in TestMemoryProfiler
- Auto-submitted: auto-generated
- References: <bug-64999-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64999
--- Comment #28 from boger at us dot ibm.com ---
I'm not concerned about the inline case. The user could build without inlining
if it was important.
To me it seems like you don't want libbacktrace to decrement the pc when it is
being called by runtime.Callers. Then runtime.Callers should be correct and no
changes needed for pprof.go. But I suppose that messes up other users of
libbacktrace unless you somehow had a way to indicate not to decrement in this
case or to create a different unwind callback function.