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
Yes, there are certainly gaps I was going to hold off finalising atomics codegen until the memory model working group finalise the C++ mappings (as then I can get the whole thing reviewed by the RISC-V memory model people), but this seems to be taking longer than expected. Once I've caught up on code reviews and made more progress in merging F+D codegen upstream I should be able to take another look at this.
Reacted by sunnystormy, Steyn Huurman, Elahn Ientile and Ariel Núñez
Activity
asb commentedon Feb 27, 2018
Yes, there are certainly gaps I was going to hold off finalising atomics codegen until the memory model working group finalise the C++ mappings (as then I can get the whole thing reviewed by the RISC-V memory model people), but this seems to be taking longer than expected. Once I've caught up on code reviews and made more progress in merging F+D codegen upstream I should be able to take another look at this.
luismarques commentedon Feb 28, 2018
D's runtime library also needs more complete atomic support.