You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In cases where compiler is used in some sort of parallel compilation (e.g. sbt) statistics (if enabled) are gathered in single place. Regardless of statistics being tempered (e.g. thread A and B wants to push/pop timer: A.push B.push, A.pop B.pop and we end in B -> A for A and A ~~> B for B ~~ instead of tow medium times we got one long and one short time) it can also fails (e.g. match error on popTimer).
The text was updated successfully, but these errors were encountered:
@SethTisue Nothing happened in this area because the use of statistics within the compiler didn't require thread safety. Now, with the introduction of the parallel genbcode, the use case has changed, so I'm happy to see progress on this area in the ticket that Lukas has linked to.
@jvican what about gathering stats from IDE/sbt based compilations that run multiple compilations in parallel? IIRC the problem was that stats was stored in static maps that was shared across all compilations.
In cases where compiler is used in some sort of parallel compilation (e.g. sbt) statistics (if enabled) are gathered in single place. Regardless of statistics being tempered (e.g. thread A and B wants to push/pop timer: A.push B.push, A.pop B.pop and we end in B -> A for A and A ~~> B for B ~~ instead of tow medium times we got one long and one short time) it can also fails (e.g. match error on popTimer).
The text was updated successfully, but these errors were encountered: