https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113807
--- Comment #8 from rhalbersma ---
For bitset::operator==, I wonder why (at last in C++20 and later mode) it is
not defaulted?
For bitset::set and bitset::operator==, I also wonder why the manual loop vs
memset/memcmp consteval logic is not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113807
--- Comment #3 from rhalbersma ---
Nice that this is changed now. I noticed a similar optimization could be done
for bitset::operator== (more accurately: the helper _M_is_equal) where there is
an opportunity to use memcmp, with a similar dance
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113807
Bug ID: 113807
Summary: [performance] bitset::set not using memset opportunity
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113806
Bug ID: 113806
Summary: [performance] bitset::operator>>= unnecessarily
sanitizes the high-word
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108260
Bug ID: 108260
Summary: __cpp_lib_ranges_zip feature test macro not defined
while std::views::zip is supported
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93480
--- Comment #9 from rhalbersma ---
Could this fix also be back-ported to gcc 10?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94924
--- Comment #4 from rhalbersma ---
Is there any chance that this bug fix can be backported to gcc 10 also?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108214
Bug ID: 108214
Summary: writinng bitset to stringstream fails
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
