Bug 17118 – [REG 2.074a] iasm64.d in test suite with with -g reveals a regression

Related to the newCTFE engine: IRC: --- <uplink|dmd> DotBatch, alphaglosined or someone else [10:58] <uplink|dmd> please report that there are issues with iasm then compiled with -g and a ~master dmd [10:58] <uplink|dmd> this is a serious regression [10:59] <DotBatch> I'd take the token but I'd like to verify before. That's why I tried to build a few minutes ago [10:59] <DotBatch> eg. a small program to reproduce the issue [11:00] <uplink|dmd> iasm64.d from the test-suite should be enough [11:00] <uplink|dmd> this something only walter can fix efficiently I think [11:00] <DotBatch> But it should be visible from the autotester then, everything should becomes red in the next hours [11:00] --> markos_ ([email protected]) a rejoint ce canal. [11:00] <uplink|dmd> no [11:01] <uplink|dmd> because dmd does not compile with -g [11:01] <uplink|dmd> and the auto-tester does not compile dmd with the freshly compiled dmd [11:01] <-- aermicioi ([email protected]) a quitté ce serveur (Ping timeout: 240 seconds). [11:01] <uplink|dmd> it will only show up on travis [11:01] <uplink|dmd> and only if someone tests it with -g --- You should see the problem by running the test suite with the -g flag.

Could you use Digger to bisect what commit introduced the problem? https://github.com/CyberShadow/Digger Also Dustmite is a useful tool to minimize the test case first. https://github.com/CyberShadow/Dustmite

contact [email protected] to get a clean report. This was reported indirectly.