https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
--- Comment #39 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Randy from comment #38) > std::string is not thread safe, this is why vstring is used (from my > memory). That's totally wrong, vstring has no more thread-safety than std::string has. The same rules apply to both of them (it's OK to call const member functions concurrently, but any non-const access must be manually synchronized by the caller).
