|
|
|
|
|
|
by pixelesque
1 hour ago
|
|
|
Or just raw pointers, indeed. std::shared_ptrs can also (because they're implicitly for sharing) alias, so the compiler has to assume the worst and emit loads in other cases, and there's no way (unless a newer C++ version has introduced it and I haven't noticed?) to use '__restrict__' with shared ptrs. |
|
|