Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
There are some examples on the Internet of people declaring their variables both volatile and __thread. I think it’s a mistake because __thread implies that there’s a copy for each thread, so with volatile the “best” you can do is disable caching of such variable, for some obscure reasons. Am I missing something?
The two terms are not mutually exclusive.
volatileis not only used in matters of multi-threading, it’s used for any situation the variable might change without the current code block being aware — such as callback functions, or signal handlers.