|--- |FIXED
--- Comment #7 from Dlang Bot ---
dlang/dmd pull request #9658 "fix issue 18794 - Compiling with -O causes
runtime segfault" was merged into master:
- 067645189191f9739e7151f2b02275ab3ea65557 by aG0aep6G:
fix issue 18794 - Compiling with -O causes runtime segfault
J
---
@aG0aep6G created dlang/dmd pull request #9658 "fix issue 18794 - Compiling
with -O causes runtime segfault" fixing this issue:
- fix issue 18794 - Compiling with -O causes runtime segfault
Just adding a test. The issue has apparently been fixed by
d80e14ba6037373f08c6dba274368408932d9e
https://issues.dlang.org/show_bug.cgi?id=18794
--- Comment #5 from ag0aep6g ---
(In reply to ag0aep6g from comment #1)
> bitIdx is a DWORD at rbp-0x10. But later a QWORD is read from there and used
> in the bt instruction. So that reads garbage from the stack. The garbage can
https://issues.dlang.org/show_bug.cgi?id=18794
--- Comment #4 from hst...@quickfur.ath.cx ---
Just tested in my environment, -inline does indeed make the problem go away.
(Mask it, probably.)
However, I can still reproduce the problem with just -O, even though the
original problem was discovered
https://issues.dlang.org/show_bug.cgi?id=18794
Jonathan M Davis changed:
What|Removed |Added
CC|
https://issues.dlang.org/show_bug.cgi?id=18794
--- Comment #2 from hst...@quickfur.ath.cx ---
Just a side-note that although in my own environment, the problem can be
reproduced with -O alone, apparently in some other environments specifying both
-O and -profile is necessary to trigger the bug.
https://issues.dlang.org/show_bug.cgi?id=18794
ag0aep6g changed:
What|Removed |Added
CC||ag0ae...@gmail.com
https://issues.dlang.org/show_bug.cgi?id=18794
hst...@quickfur.ath.cx changed:
What|Removed |Added
Keywords||wrong-code
--