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

Mike Franklin <slavo5150@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WORKSFORME

--

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

Walter Bright <bugzilla@digitalmars.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |industry

--

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

ag0aep6g <ag0aep6g@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |---

--- Comment #9 from ag0aep6g <ag0aep6g@gmail.com> ---
(In reply to Mike Franklin from comment #7)
> According to https://run.dlang.io/is/98Uf5T, this has been working since 2.067.1.

Fails on run.dlang.io when you compile with -c. https://run.dlang.io/is/gnOvlp

(In reply to Mike Franklin from comment #8)
> According to https://run.dlang.io/is/kosY23, this has been fixed since 2.070.2

Ditto. https://run.dlang.io/is/UCl87z

On my machine, both versions fail with and without -c. Maybe the bug is somewhat nondeterministic? It's consistently reproducible for me, though.

Reopening.

--

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

Basile B. <b2.temp@gmx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |greeenify@gmail.com

--- Comment #10 from Basile B. <b2.temp@gmx.com> ---
Still reproducible here too.

I think that it works online because -g is added to the switches so that the object can be disasm and displayed. You can try on your machines with -g an you'll see that the ICE doesn't appear.

Seb, do you confirm that run.dlang.io adds -g ?

--

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

Seb <greensunny12@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |greensunny12@gmail.com

--- Comment #11 from Seb <greensunny12@gmail.com> ---
> Seb, do you confirm that run.dlang.io adds -g ?

Yes, -g is always added except if you just use -c

https://github.com/dlang-tour/core-exec/blob/master/entrypoint.sh

So the failure is still there:

https://run.dlang.io/is/8NVvW1

All compilers (called dreg) is a different image, but again omits -g only for
-g:

https://github.com/dlang-tour/core-dreg/blob/master/entrypoint.sh

--

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

Walter Bright <bugzilla@digitalmars.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Hardware|x86_64                      |All
                 OS|Linux                       |All

--

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

--- Comment #12 from Walter Bright <bugzilla@digitalmars.com> ---
https://github.com/dlang/dmd/pull/8078

--

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

--- Comment #13 from github-bugzilla@puremagic.com ---
Commits pushed to master at https://github.com/dlang/dmd

https://github.com/dlang/dmd/commit/6c42ce082744e721bba802e5dae96dc0ed6c598f fix Issue 16107 - [ICE] - Internal error: backend/cgcod.c 2297

https://github.com/dlang/dmd/commit/7d79100827427ce6fecc33a533999c7d93f857b6 Merge pull request #8078 from WalterBright/fix16107

fix Issue 16107 - [ICE] - Internal error: backend/cgcod.c 2297

--

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

github-bugzilla@puremagic.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--