https://llvm.org/bugs/show_bug.cgi?id=26856
Bug ID: 26856
Summary: clang 3.8.0/powerpc's _Unwind_RaiseException code
generation has messed up r31 (frame pointer)
save/restore code (SEGV's can result)
Product: clang
Version: 3.8
Hardware: Other
OS: FreeBSD
Status: NEW
Severity: normal
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: mar...@dsl-only.net
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
Classification: Unclassified
The below causes gdb difficulties for its stack handling: more than just
exception handling is at issue. I just happened to notice it via exception
handling.
Function _Unwind_RaiseException below is from a FreeBSD "buildworld" using
clang 3.8.0.
Dump of assembler code for function _Unwind_RaiseException:
0x41b2ab80 <+0>: mflr r0
0x41b2ab84 <+4>: stw r31,-148(r1)
0x41b2ab88 <+8>: stw r30,-152(r1)
0x41b2ab8c <+12>: stw r0,4(r1)
0x41b2ab90 <+16>: stwu r1,-2992(r1)
0x41b2ab94 <+20>: mr r31,r1
. . .
0x41b2abe0 <+96>: stw r31,2844(r31)
(which replaces the earlier save of the old Frame pointer R31
value with a copy of r1's current value. Note the offset
relationships with the r1 adjustment: -2992+2844=-148)
. . .
0x41b2add0 <+592>: lwz r31,2844(r31)
(This restores the r1 value that resulted from the "stwu r1,-2992(r1)" into
R31.)
. . .
0x41b2ae30 <+688>: lwz r31,-148(r1)
(This restores the r1 value that resulted from the "stwu r1,-2992(r1)" into
R31.)
. . .
The wrong r31 value is present when _Unwind_RaiseException returns.
But before that while _Unwind_RaiseException is active the C++ exception
handling infrastructure has been given bad r31 information for around
_Unwind_RaiseException's frame.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
