https://bugs.llvm.org/show_bug.cgi?id=40795
Jeremy Morse <jeremy.morse.l...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Fixed By Commit(s)| |359426
Resolution|--- |FIXED
--- Comment #10 from Jeremy Morse <jeremy.morse.l...@gmail.com> ---
Fixed in 359426; the variable 'l_34' now reads 'optimized out' in gdb, which is
the most we can hope for in the optimised code: the variable does not have a
machine location when optimize_me_not is called, and thus there's no way to
recover what the variable would have been in the original program.
The likely-dupe program in comment 7 appears to be fixed too -- or at least on
the call to f, l_1412 reads as 947, which IIRC is the correct behaviour.
This was almost certainly misleading developers, many thanks for the report!
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
