Conversation
relacy/relacy_std.hpp
Outdated
| using rl::mo_release; | ||
| using rl::mo_acq_rel; | ||
| using rl::mo_seq_cst; | ||
| namespace rlimp { |
|
What compiler are you using? And what warnings does it produce? |
|
I had some std header included (vector, string) and on Visual Studio 2015 it was complaining about the memory_order: On GCC (5, the current mainstream gcc compiler on ubuntu) it had a similar problem with the atomic. |
| //# define atomic_intmax_t rlimp::atomic_intmax_t | ||
| //# define atomic_uintmax_t mutex rlimp::atomic_uintmax_t | ||
|
|
||
| # define mutex rlimp::mutex |
There was a problem hiding this comment.
Does mutex lead to the same problems?
It's pretty common name, so redefining it is unfortunate...
|
It was a fast search/replace and did not considered any other name conflict. Note, I had the define problem with delete too. |
So does mutex lead to the same problems or not?
Just don't use this with Relacy. |
|
mutex was ok, did not have the problem. |
git push -f?
Yes. It fixes build for you, right? Thanks |
Due to forward declarations and the structure of std includes I had compiler warning for redeclaring some atomic structures.
Here is a possible solution using defines and an internal namespace in std.