[Issue 15573] -O -inline causes wrong code with idiv instruction

https://issues.dlang.org/show_bug.cgi?id=15573 --- Comment #28 from yebblies --- (In reply to hsteoh from comment #27) > Argh you're right, I missed that... that'll teach me to analyze assembly > code without stepping through it in a debugger... Honestly I didn't know that

[Issue 15588] New: Improve DMD -L switch documentation

https://issues.dlang.org/show_bug.cgi?id=15588 Issue ID: 15588 Summary: Improve DMD -L switch documentation Product: D Version: D2 Hardware: x86 OS: Windows Status: NEW Severity: enhancement

[Issue 15567] local import hijacking

https://issues.dlang.org/show_bug.cgi?id=15567 hst...@quickfur.ath.cx changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 10378] Local imports hide local symbols

https://issues.dlang.org/show_bug.cgi?id=10378 hst...@quickfur.ath.cx changed: What|Removed |Added CC||bhe...@moxiegroup.com --- Comment

[Issue 15573] -O -inline causes wrong code with idiv instruction

https://issues.dlang.org/show_bug.cgi?id=15573 --- Comment #29 from hst...@quickfur.ath.cx --- Alright, I think I found the real culprit now. Still referencing the asm dump I posted, the problematic spot is here: ... 438cb8: 31 f6 xor%esi,%esi 438cba: 64 48

[Issue 15573] -O -inline causes wrong code with idiv instruction

https://issues.dlang.org/show_bug.cgi?id=15573 --- Comment #27 from hst...@quickfur.ath.cx --- Argh you're right, I missed that... that'll teach me to analyze assembly code without stepping through it in a debugger... --

[Issue 15586] std.utf.toUTF8() segfaults when fed an invalid dchar

https://issues.dlang.org/show_bug.cgi?id=15586 --- Comment #6 from thomas.bock...@gmail.com --- I may have reduced this one too far: https://github.com/D-Programming-Language/phobos/pull/3943#issuecomment-173381348 Arguably, the real bug is that certain other functions in Phobos call

[Issue 15582] Slice returned by opSlice() not accepted as lvalue

https://issues.dlang.org/show_bug.cgi?id=15582 --- Comment #3 from b2.t...@gmx.com --- (In reply to Marc Schütz from comment #2) > (In reply to b2.temp from comment #1) > > I don't aggree, it's like if you say that > > > > s.opSlice() = 10; > > > > should work. > > That should work, too. > >

[Issue 15582] Slice returned by opSlice() not accepted as lvalue

https://issues.dlang.org/show_bug.cgi?id=15582 hst...@quickfur.ath.cx changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 15584] Security issue: symlink attack

https://issues.dlang.org/show_bug.cgi?id=15584 --- Comment #10 from Cédric Picard --- (In reply to Ketmar Dark from comment #9) > which, of course, can be caused by many other reasons. like, for example, > remounting (rebinding) output point (which can be caused by some

[Issue 15584] Security issue: symlink attack

https://issues.dlang.org/show_bug.cgi?id=15584 --- Comment #6 from Cédric Picard --- @ketmar This not an issue about executing code. This is a case where the victim doesn't have to execute *any* line of the given program, not one line, compiling it is enough to be

[Issue 15584] Security issue: symlink attack

https://issues.dlang.org/show_bug.cgi?id=15584 --- Comment #8 from Cédric Picard --- (In reply to Ketmar Dark from comment #7) > (In reply to Cédric Picard from comment #6) > > Otherwise > > why did we bother enforce that the compiler can't read or write arbitrary > >

[Issue 15584] Security issue: symlink attack

https://issues.dlang.org/show_bug.cgi?id=15584 Ketmar Dark changed: What|Removed |Added Severity|critical|enhancement --

[Issue 15584] Security issue: symlink attack

https://issues.dlang.org/show_bug.cgi?id=15584 Ketmar Dark changed: What|Removed |Added CC|

[Issue 15584] Security issue: symlink attack

https://issues.dlang.org/show_bug.cgi?id=15584 Ketmar Dark changed: What|Removed |Added Severity|enhancement |normal --- Comment

[Issue 15584] Security issue: symlink attack

https://issues.dlang.org/show_bug.cgi?id=15584 --- Comment #9 from Ketmar Dark --- (In reply to Cédric Picard from comment #8) > If anything to bring some consistency. Security issues appart compiling the > same source code with the same flags and the same files in the

[Issue 15589] New: extern(C++) virtual destructors are not put in vtbl[]

https://issues.dlang.org/show_bug.cgi?id=15589 Issue ID: 15589 Summary: extern(C++) virtual destructors are not put in vtbl[] Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: enhancement

[Issue 15579] extern(C++) interfaces/multiple-inheritance

https://issues.dlang.org/show_bug.cgi?id=15579 --- Comment #4 from Walter Bright --- https://issues.dlang.org/show_bug.cgi?id=15589 remains, though. --

[Issue 15579] extern(C++) interfaces/multiple-inheritance

https://issues.dlang.org/show_bug.cgi?id=15579 --- Comment #3 from Walter Bright --- https://github.com/D-Programming-Language/dmd/pull/5361 --

[Issue 12822] Delegate .ptr assignment considered @safe

https://issues.dlang.org/show_bug.cgi?id=12822 Mike Wey changed: What|Removed |Added CC|m...@mikewey.eu | --

[Issue 15573] -O -inline causes wrong code with idiv instruction

https://issues.dlang.org/show_bug.cgi?id=15573 yebblies changed: What|Removed |Added CC||yebbl...@gmail.com ---

[Issue 15579] extern(C++) interfaces/multiple-inheritance

https://issues.dlang.org/show_bug.cgi?id=15579 Walter Bright changed: What|Removed |Added CC|