[llvm-bugs] [Bug 38857] [codeview] Incorrect variable locations with stack realignment and call-frame optimization
via llvm-bugs
llvm-bugs at lists.llvm.org
Mon Nov 5 13:51:24 PST 2018
https://bugs.llvm.org/show_bug.cgi?id=38857
Reid Kleckner <rnk at google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #16 from Reid Kleckner <rnk at google.com> ---
I confirmed that the offsets changed in r346062, here's the symbol records
before and after:
0 | S_LOCAL [size = 26] `remaining_bytes`
type=0x0023 (unsigned __int64), flags = none
0 | S_DEFRANGE_FRAMEPOINTER_REL [size = 16]
offset = -12, range = [0000:0029,+343)
gaps = 2
0 | S_LOCAL [size = 32] `remaining_bytes_again`
type=0x0023 (unsigned __int64), flags = none
0 | S_DEFRANGE_FRAMEPOINTER_REL [size = 16]
offset = -20, range = [0000:0029,+343)
gaps = 2
after:
0 | S_LOCAL [size = 26] `remaining_bytes`
type=0x0023 (unsigned __int64), flags = none
0 | S_DEFRANGE_FRAMEPOINTER_REL [size = 16]
offset = -16, range = [0000:0029,+343)
gaps = 2
0 | S_LOCAL [size = 32] `remaining_bytes_again`
type=0x0023 (unsigned __int64), flags = none
0 | S_DEFRANGE_FRAMEPOINTER_REL [size = 16]
offset = -24, range = [0000:0029,+343)
gaps = 2
I had some trouble getting windbg to stop at the same point again, but
eventually I succeeded and now I see this:
0:029> dv
this = 0x11a43950
remaining_bytes = 0x15aa48
remaining_bytes_again = 0x00000012`346678ab
items = <value unavailable>
That looks right, so I'd say this is fixed. It should be in the next clang roll
which is tracked at https://crbug.com/894363
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20181105/e689ad38/attachment.html>
More information about the llvm-bugs
mailing list