[Bug libstdc++/116549] std::disable_sized_sentinel_for is missing specialisation for std::move_iterator

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116549 --- Comment #6 from Zhao Dai --- Thanks for the explanation, Jonathan! I agree that `sized_sentinel_for` is the right way to check sized sentinel. >From the source of `sized_sentinel_for` (https://github.com/gcc-mirror/gcc/blob/master/libstdc%

[Bug libstdc++/116549] std::disable_sized_sentinel_for is missing specialisation for std::move_iterator

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116549 --- Comment #3 from Zhao Dai --- Thanks for the reply! I tested on Compiler Explorer (https://godbolt.org/z/EKxhvKoez, GCC trunk, -std=c++23). And > I couldn't find it in any of the current GCC source, especially > *libstdc++-v3/include/bits/

[Bug libstdc++/116549] std::disable_sized_sentinel_for is missing specialisation for std::move_iterator

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116549 --- Comment #1 from Zhao Dai --- Just found a report in 2022: https://cplusplus.github.io/LWG/issue3736 Unfortunately, it's not resolved yet despite it seems an easy fix.

[Bug libstdc++/116549] New: std::disable_sized_sentinel_for is missing specialisation for std::move_iterator

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116549 Bug ID: 116549 Summary: std::disable_sized_sentinel_for is missing specialisation for std::move_iterator Product: gcc Version: 14.2.1 Status: UNCONFIRMED Sever

[Bug libstdc++/116455] Should std::noop_coroutine() be constexpr?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116455 --- Comment #5 from Zhao Dai --- (In reply to Andrew Pinski from comment #4) > (In reply to Zhao Dai from comment #3) > > I understand that the standard says so. > > > > But the question is: Should it? > > This is not the correct forum for tha

[Bug libstdc++/116455] Should std::noop_coroutine() be constexpr?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116455 Zhao Dai changed: What|Removed |Added CC||daidodo at gmail dot com --- Comment #3 from

[Bug c++/116168] Segmentation fault when compiling user-defined partial_ordering

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116168 Zhao Dai changed: What|Removed |Added CC||daidodo at gmail dot com --- Comment #2 from

[Bug libstdc++/116455] New: Should std::noop_coroutine() be constexpr?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116455 Bug ID: 116455 Summary: Should std::noop_coroutine() be constexpr? Product: gcc Version: 14.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lib

[Bug libstdc++/116342] The compiler doesn't respect customised strong_order/weak_order for floating point types.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116342 --- Comment #4 from Zhao Dai --- > floating point is a fundamental types so there is no ADL involved ... Thanks for pointing out! I checked other types (int/bool/nullptr_t/type alias/...), and it seems all builtin types and their alias are excl

[Bug c++/116342] New: The compiler doesn't respect customised strong_order/weak_order for floating point types.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116342 Bug ID: 116342 Summary: The compiler doesn't respect customised strong_order/weak_order for floating point types. Product: gcc Version: 14.1.0 Status: UNCONFIRMED

[Bug c++/116168] New: Segmentation fault when compiling user-defined partial_ordering

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116168 Bug ID: 116168 Summary: Segmentation fault when compiling user-defined partial_ordering Product: gcc Version: 14.1.0 Status: UNCONFIRMED Severity: normal