Thread overview
[Bug 290] ice-on-valid: Assertion `fd->semanticRun == PASSsemantic3done' failed.
Apr 15, 2018
Iain Buclaw
Apr 15, 2018
Sebastien Alaiwan
Apr 16, 2018
Iain Buclaw
April 15, 2018
https://bugzilla.gdcproject.org/show_bug.cgi?id=290

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #1 from Iain Buclaw <ibuclaw@gdcproject.org> ---
Not reproducible on master, may have been a frontend bug that was backported from the 2.076-compat patches.

-- 
You are receiving this mail because:
You are watching all bug changes.
April 15, 2018
https://bugzilla.gdcproject.org/show_bug.cgi?id=290

--- Comment #2 from Sebastien Alaiwan <sebastien.alaiwan@gmail.com> ---
(In reply to Iain Buclaw from comment #1)
> Not reproducible on master, may have been a frontend bug that was backported from the 2.076-compat patches.

Yeah, maybe ; please keep in mind this one is highly volatile.

For example, I can prevent the problem from manifesting itself by simply deleting the declaration of the (unused) structure "Context".

The error might still be present on master (but would need a slightly different
test case).

-- 
You are receiving this mail because:
You are watching all bug changes.
April 16, 2018
https://bugzilla.gdcproject.org/show_bug.cgi?id=290

--- Comment #3 from Iain Buclaw <ibuclaw@gdcproject.org> ---
(In reply to Sebastien Alaiwan from comment #2)
> (In reply to Iain Buclaw from comment #1)
> > Not reproducible on master, may have been a frontend bug that was backported from the 2.076-compat patches.
> 
> Yeah, maybe ; please keep in mind this one is highly volatile.
> 
> For example, I can prevent the problem from manifesting itself by simply deleting the declaration of the (unused) structure "Context".
> 
> The error might still be present on master (but would need a slightly
> different test case).

Can this be reproduced in any version of dmd between 2.068 and 2.076?

That would be one way to check, but as this is not a context-free test, it could even be that library changes made the bug go away.

-- 
You are receiving this mail because:
You are watching all bug changes.