[Issue 13742] undefined reference to __coverage

2018-01-15 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13742 --- Comment #8 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/69e7bd18892df18f682906916bf8c8ad87fb30e5 fix Issue 13742 - undefined reference to __coverage - Nested

[Issue 13742] undefined reference to __coverage

2018-01-15 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13742 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|-

[Issue 13742] undefined reference to __coverage

2018-01-09 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13742 Martin Nowak changed: What|Removed |Added Keywords||pull --- Comment #7 from Martin Nowak --- ht

[Issue 13742] undefined reference to __coverage

2018-01-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13742 --- Comment #6 from Martin Nowak --- The problem seems to be that the `performLocked!(() => foo);` has a location in bar.d and tries to increment bar's location, but the bar object is already emitted. When objects are done all symbols get reset and f

[Issue 13742] undefined reference to __coverage

2018-01-06 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13742 --- Comment #5 from Martin Nowak --- Apparently happens because the __coverage symbols is defined twice in foo.o (2.078.0), once as BSS symbols and once as undefined symbol. nm lib.a foo.o: t d __bcoverage 000

[Issue 13742] undefined reference to __coverage

2017-04-23 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13742 Les De Ridder changed: What|Removed |Added CC||dl...@lesderid.net --

[Issue 13742] undefined reference to __coverage

2016-02-03 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13742 Luís Marques changed: What|Removed |Added CC||l...@luismarques.eu --

[Issue 13742] undefined reference to __coverage

2016-02-02 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13742 Sönke Ludwig changed: What|Removed |Added CC||slud...@outerproduct.org --- Comment #4 from

[Issue 13742] undefined reference to __coverage

2015-07-24 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13742 Marc Schütz changed: What|Removed |Added CC||schue...@gmx.net --

[Issue 13742] undefined reference to __coverage

2015-04-13 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13742 Martin Nowak changed: What|Removed |Added Priority|P1 |P4 --

[Issue 13742] undefined reference to __coverage

2015-04-13 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13742 --- Comment #3 from Martin Nowak --- (In reply to jiki from comment #2) > I hit this on Windows. > Reduced test case is here. Also confirmed for linux. A temporary workaround for your case is to only generate a single object file. dmd -cov -g -c -o

[Issue 13742] undefined reference to __coverage

2015-03-28 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13742 j...@red.email.ne.jp changed: What|Removed |Added CC||j...@red.email.ne.jp --- Comment #2 fr

[Issue 13742] undefined reference to __coverage

2015-01-02 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13742 --- Comment #1 from Martin Nowak --- Another occurence of this issue. https://github.com/kiith-sa/D-YAML/issues/20 --