https://issues.dlang.org/show_bug.cgi?id=22700

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ibuclaw@gdcproject.org

--- Comment #1 from Iain Buclaw <ibuclaw@gdcproject.org> ---
Can only go as far back as the following PR in dmd before druntime no longer is compilable.

https://github.com/dlang/dmd/pull/12209

Fair amount of reduction needs to be done.

--

https://issues.dlang.org/show_bug.cgi?id=22700

Mathias LANG <pro.mathias.lang@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pro.mathias.lang@gmail.com

--- Comment #2 from Mathias LANG <pro.mathias.lang@gmail.com> ---
Currently `-checkaction=context` is not usable without `-unittest`, at least this has been our experience. It results in heaps of undefined symbols.

This is due, I believe, to Druntime being compiled with `-checkaction=D` (the
default).
See Also: https://github.com/dlang/dmd/pull/13224#discussion_r789706699

--

https://issues.dlang.org/show_bug.cgi?id=22700

moonlightsentinel@disroot.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |moonlightsentinel@disroot.o
                   |                            |rg

--- Comment #3 from moonlightsentinel@disroot.org ---
(In reply to Mathias LANG from comment #2)
> This is due, I believe, to Druntime being compiled with `-checkaction=D`

Both `-checkaction=D` and `-release` (or `-check=assert=off`) prevent the
message generation.

--

https://issues.dlang.org/show_bug.cgi?id=22700

--- Comment #4 from dlangBugzillaToGithub <robert.schadek@posteo.de> ---
THIS ISSUE HAS BEEN MOVED TO GITHUB

https://github.com/dlang/dmd/issues/20043

DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB

--