[Issue 15568] Wrong contracts generated when compiled with -O
https://issues.dlang.org/show_bug.cgi?id=15568 --- Comment #4 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/585ab7d14146ec6bc45b41e2b0b344e06dbbe1ee test Issue 15568 - Wrong contracts generated when compiled with -O https://github.com/dlang/dmd/commit/05a0edff93b611e2d67d5c77237092dd220afe75 Merge pull request #5803 from WalterBright/test15568 test Issue 15568 - Wrong contracts generated when compiled with -O --
[Issue 15568] Wrong contracts generated when compiled with -O
https://issues.dlang.org/show_bug.cgi?id=15568 Walter Brightchanged: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Walter Bright --- This passes on all platforms in the autotester. Marking it as worksforme for now. --
[Issue 15568] Wrong contracts generated when compiled with -O
https://issues.dlang.org/show_bug.cgi?id=15568 Walter Brightchanged: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment #2 from Walter Bright --- https://github.com/dlang/dmd/pull/5803 --
[Issue 15619] [REG 2.066] Floating-point x86_64 codegen regression, when involving array ops
https://issues.dlang.org/show_bug.cgi?id=15619 Walter Brightchanged: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment #6 from Walter Bright --- Doesn't seem like this should be too hard to fix - just save xmm6-7 for Win64 - why not just do it? --
[Issue 15907] Unjustified "is not visible from module" deprecation warning when using getMember trait
https://issues.dlang.org/show_bug.cgi?id=15907 Walter Brightchanged: What|Removed |Added CC||bugzi...@digitalmars.com Assignee|nob...@puremagic.com|c...@dawg.eu --
[Issue 15941] [REG v2.069] rbtree no longer supports classes
https://issues.dlang.org/show_bug.cgi?id=15941 Walter Brightchanged: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment #1 from Walter Bright --- The commit that added rbtree.toString: https://github.com/dlang/phobos/commit/0f05183f5c792ac3adbc50953a9639b0140a27fc --
[Issue 15918] [2.070] Results from findSplit can no longer be assigned to each other
https://issues.dlang.org/show_bug.cgi?id=15918 Walter Brightchanged: What|Removed |Added CC||bugzi...@digitalmars.com Assignee|nob...@puremagic.com|and...@erdani.com --
[Issue 16031] [REG2.071] dmd internal error when compiling druntime with PIC=1
https://issues.dlang.org/show_bug.cgi?id=16031 Walter Brightchanged: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment #1 from Walter Bright --- (In reply to Martin Krejcirik from comment #0) > make -f posix.mak MODEL=32 DMD=../dmd/src/dmd PIC=1 What does the PIC=1 do? PIC isn't anywhere in posix.mak --
[Issue 16065] Provide digitally signed binaries for Windows
https://issues.dlang.org/show_bug.cgi?id=16065 James King <1...@lwshost.com> changed: What|Removed |Added CC||1...@lwshost.com --
[Issue 16065] New: Provide digitally signed binaries for Windows
https://issues.dlang.org/show_bug.cgi?id=16065 Issue ID: 16065 Summary: Provide digitally signed binaries for Windows Product: D Version: D2 Hardware: All OS: Windows Status: NEW Severity: enhancement Priority: P1 Component: installer Assignee: nob...@puremagic.com Reporter: 1...@lwshost.com Hi all! Would it be possible to provide digitally signed binaries for the DMD Windows installers? Additionally, though this is likely outside the scope, perhaps [eventually] LDC and GDC installers could be hosted here as well [and signed]? Currently they are delivered over HTTP, and there is no way to be certain that the files truly originated from the downloads.dlang.org server or somewhere else. Even if HTTPS and HSTS were made available, this wouldn't protect users in a hypothetical scenario where the web server itself was compromised or where a Man-in-the-Middle attack had replaced the D website with another website that had a 'valid certificate' issued by another CA. I realize that this may be tricky to add into the build/release process, as protecting the signing key now becomes a critical issue, but I wanted to bring it up as I saw no previous or existing issues that covered this topic. Thank you for your consideration. --
[Issue 16064] New: std.experimental.allocator.dispose can't be used in @nogc blocks
https://issues.dlang.org/show_bug.cgi?id=16064 Issue ID: 16064 Summary: std.experimental.allocator.dispose can't be used in @nogc blocks Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: major Priority: P1 Component: phobos Assignee: nob...@puremagic.com Reporter: b2.t...@gmx.com There's a flaw, the following code doesn't compile, even if Mallocator is 100% @nogc and that the __dtor is @nogc import std.experimental.allocator; import std.experimental.allocator.mallocator; class Foo { ~this()@nogc {} } void main() @nogc { Foo foo = make!Foo(Mallocator.instance); dispose(Mallocator.instance, foo); } The problem is due to dispose() that calls destroy() which is not a template and thus cannot infer the attributes. A possible fix is to write a custom destroy() that would call __dtor or __xdtor, at least for classes and pointer to structs, as a template, and used in dispose(). --
[Issue 15831] IFTI voldemort type exploding bloat
https://issues.dlang.org/show_bug.cgi?id=15831 --- Comment #6 from ZombineDev--- For anyone who want to try a new scheme for reducing the symbol size: have a look at the test case for issue 16039 where a simple change makes the binary size explode from 18MB to over 400MB. https://issues.dlang.org/show_bug.cgi?id=16039 --