[Issue 16724] New: RandomCover.popFront is a no-op for the first call

https://issues.dlang.org/show_bug.cgi?id=16724 Issue ID: 16724 Summary: RandomCover.popFront is a no-op for the first call Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: normal

[Issue 13927] optimizer hangs in optelem with SIMD initialization

https://issues.dlang.org/show_bug.cgi?id=13927 Walter Bright changed: What|Removed |Added Keywords||pull

[Issue 16711] New: unittest writefln

https://issues.dlang.org/show_bug.cgi?id=16711 Issue ID: 16711 Summary: unittest writefln Product: D Version: D2 Hardware: x86 OS: Windows Status: NEW Severity: enhancement Priority: P1

[Issue 12429] SIMD vector type errors are too eager

https://issues.dlang.org/show_bug.cgi?id=12429 yebblies changed: What|Removed |Added Resolution|WONTFIX |DUPLICATE --- Comment #6

[Issue 8425] Missing line number and module name that can't use core.simd

https://issues.dlang.org/show_bug.cgi?id=8425 yebblies changed: What|Removed |Added CC||john.loughran.colvin@gmail.

[Issue 8047] important opcodes missing from core/simd.d

https://issues.dlang.org/show_bug.cgi?id=8047 Marco Leise changed: What|Removed |Added Status|RESOLVED|REOPENED

[Issue 12430] non compile-time __simd opcode causes ICE

https://issues.dlang.org/show_bug.cgi?id=12430 Walter Bright changed: What|Removed |Added Keywords||pull --- Comment

[Issue 13851] ICE with simd assignment to void16 vector

https://issues.dlang.org/show_bug.cgi?id=13851 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 16611] std.traits.fullyQualifiedName fails with error 'Unrecognized type const(void)'

https://issues.dlang.org/show_bug.cgi?id=16611 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 16611] std.traits.fullyQualifiedName fails with error 'Unrecognized type const(void)'

https://issues.dlang.org/show_bug.cgi?id=16611 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/a636bb6bb00e54fda367bd3c452db2ced0ca9df6 Fix Issue 16611 - 'Unrecognized type const(void)' error

[Issue 16699] [REG 2.070] stack corruption with scope(exit)

https://issues.dlang.org/show_bug.cgi?id=16699 --- Comment #17 from Steven Schveighoffer --- (In reply to Ketmar Dark from comment #15) > the whole process is broken: under no circumstances any hotfix that is > applicable both to master and to stable can land in stable

[Issue 16699] [REG 2.070] stack corruption with scope(exit)

https://issues.dlang.org/show_bug.cgi?id=16699 --- Comment #16 from Steven Schveighoffer --- (In reply to Ketmar Dark from comment #15) > the whole process is broken: under no circumstances any hotfix that is > applicable both to master and to stable can land in stable

[Issue 5995] string append negative integer causes segfault

https://issues.dlang.org/show_bug.cgi?id=5995 Lucia Cojocaru changed: What|Removed |Added Assignee|nob...@puremagic.com

[Issue 5995] string append negative integer causes segfault

https://issues.dlang.org/show_bug.cgi?id=5995 --- Comment #15 from Steven Schveighoffer --- Lucia, I think nothing should implicitly cast to dchar. Not bool, int, or even char or wchar. But something this drastic needs approval from Walter and Andrei. Of course, we

[Issue 16699] [REG 2.070] stack corruption with scope(exit)

https://issues.dlang.org/show_bug.cgi?id=16699 --- Comment #9 from ag0ae...@gmail.com --- *** Issue 16698 has been marked as a duplicate of this issue. *** --

[Issue 16698] std.regex.matchFirst corrupts stack

https://issues.dlang.org/show_bug.cgi?id=16698 ag0ae...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 5995] string append negative integer causes segfault

https://issues.dlang.org/show_bug.cgi?id=5995 Lucia Cojocaru changed: What|Removed |Added CC|

[Issue 5995] string append negative integer causes segfault

https://issues.dlang.org/show_bug.cgi?id=5995 Lucia Cojocaru changed: What|Removed |Added Component|druntime|dmd --

[Issue 5995] string append negative integer causes segfault

https://issues.dlang.org/show_bug.cgi?id=5995 --- Comment #16 from Andrei Alexandrescu --- This bug has a simple fix - throw a runtime exception (e.g. by onUnicodeError) instead of assert(0). We shouldn't change language rules on account of this. Thanks! --

[Issue 16699] [REG 2.070] stack corruption with scope(exit)

https://issues.dlang.org/show_bug.cgi?id=16699 --- Comment #11 from hst...@quickfur.ath.cx --- 'cos this is not yet working in git HEAD. --

[Issue 16699] [REG 2.070] stack corruption with scope(exit)

https://issues.dlang.org/show_bug.cgi?id=16699 --- Comment #10 from hst...@quickfur.ath.cx --- Is it customary to close bugs once they are fixed in stable, even though the fix has not yet been merged to git HEAD? --

[Issue 16699] [REG 2.070] stack corruption with scope(exit)

https://issues.dlang.org/show_bug.cgi?id=16699 Ketmar Dark changed: What|Removed |Added See Also|https://issues.dlang.org/sh |

[Issue 16102] [REG2.070] struct dtor replace value on stack

https://issues.dlang.org/show_bug.cgi?id=16102 Ketmar Dark changed: What|Removed |Added See Also|https://issues.dlang.org/sh |

[Issue 5995] string append negative integer causes segfault

https://issues.dlang.org/show_bug.cgi?id=5995 --- Comment #17 from Steven Schveighoffer --- There are two problems, one is that the OP's code compiles, the other is that it segfaults. Arguably, fixing the first problem will fix the second. But just fixing the second leaves

[Issue 16699] [REG 2.070] stack corruption with scope(exit)

https://issues.dlang.org/show_bug.cgi?id=16699 --- Comment #18 from hst...@quickfur.ath.cx --- @Steven: I see your point about preventing redundant fixes. But it's still confusing that a bug has been resolved as fixed, yet the bug persists in master. :-) Is there a way for bugzilla to indicate

[Issue 16699] [REG 2.070] stack corruption with scope(exit)

https://issues.dlang.org/show_bug.cgi?id=16699 --- Comment #19 from Ketmar Dark --- actually, i believe that no merges from stable to master should be done at all. if hotfix is applicable to both branches, it should go to both branches, first in master, and then,

[Issue 16699] [REG 2.070] stack corruption with scope(exit)

https://issues.dlang.org/show_bug.cgi?id=16699 --- Comment #14 from hst...@quickfur.ath.cx --- Eventually all fixes in stable get merged to master. It's just that in the interim, I'm wondering whether bugs that still exist in master should be kept open until the merge happens, or as soon as

[Issue 16699] [REG 2.070] stack corruption with scope(exit)

https://issues.dlang.org/show_bug.cgi?id=16699 --- Comment #15 from Ketmar Dark --- the whole process is broken: under no circumstances any hotfix that is applicable both to master and to stable can land in stable first. --

[Issue 16705] TaskPool.reduce fails to compile "cannot get frame pointer to D main"

https://issues.dlang.org/show_bug.cgi?id=16705 ZombineDev changed: What|Removed |Added Status|RESOLVED|REOPENED