PulkoMandy 899e0ef82b userlandfs: use std::bitset for FSCapabilities ... gcc 13 is confused by the custom bitset implementation, so use the C++ standard one instead. However, this results in including the C++ <string> header in kernel code. This doesn't work for gcc2, because of two problems: - That header includes a declaration of atomic_add that doesn't match the one in SupportsDefs.h (which can in some cases replace the function with a #define for an inline version). Adjust the header to use the be a problem because it creates a risk of circular inclusions. Standard C++ headers shouldn't depend on BeAPI ones. - It also leads to the inclusion of iostream which defined lock and unlock functions in the global namespace. We don't want these, and they are not part of the C++ standard, so just remove them. Ideally we could use std::hash for the GetHashCode implementation, but that doesn't work because it depends on an helper function that's in libstdc++, and we can't link that from kernel add-ons. Change-Id: Iee07280beb4dddf7a9b6160e37f3b816e4de89ae Reviewed-on: https://review.haiku-os.org/c/haiku/+/6663 Reviewed-by: Niels Sascha Reedijk <niels.reedijk@gmail.com> Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org>		2023-07-10 06:27:18 +00:00
..
bastring.cc
bastring.h
complext.cc
complext.h
dcomplex.h
fcomplex.h
gslice_array.h
gslice.h
indirect_array.h
ldcomplex.h
mask_array.h
slice_array.h
slice.h
std_valarray.h
straits.h
valarray_array.h
valarray_array.tcc
valarray_meta.h