http://bugzilla.gdcproject.org/show_bug.cgi?id=32
--- Comment #5 from Iain Buclaw <ibuc...@gdcproject.org> 2013-04-06 17:27:27 UTC --- (In reply to comment #4) > 2 are fixed but I've not verified if they were fixed by the GC changes. > I'll try to reduce the other two segvs and file new bug reports for them. > > Overall the situation is much better now with only 13 failing tests: > std.complex:663 FAILED > std.complex:683 FAILED > std.typecons:3281 FAILED > std.range:2953 FAILED > std.range:8640 FAILED > std.math:327 FAILED > std.math:441 FAILED > std.math:1517 FAILED > std.math:1528 FAILED > std.math:1632 FAILED > std.math:2999 FAILED > std.conv:2487 FAILED > std.conv:2622 FAILED > Total results: Passed 1892 Failed 13 Disabled 2 > > ./unittest --show-disabled > std.container:3623 > std.algorithm:1721 > > Here's my fork with the "enhanced" unit test support in case you want to try > it: > https://github.com/jpf91/GDC/commits/newUnittest Ah, but do they cause gdc to SEGV, or do they SEGV during runtime? The fixes I did addressed SEGV during compilation of those two files you've shown to be disabled. -- Configure bugmail: http://bugzilla.gdcproject.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
