On Saturday, 25 April 2015 at 16:28:24 UTC, Timo Sintonen wrote:
My work is based on the feature that a shared variable is marked as volatile in gcc. This feature is buggy and should not be used in the future.
I think volatileLoad and volatileStore are intended for this (please correct me if my understanding is wrong).
The official way is to use library functions to access registers but I think this results to horrible looking code.
Are these library functions the above mentioned volatileLoad / volatileStore ?
Someone might then make an sample driver and after discussion we all could start write drivers the same way.
I Agree. It would just be plain typing-till-your-fingers-hurt after that. ;)
