[Bug libstdc++/100381] [11/12 Regression] new static_assert((std::__is_complete_or_unbounded(...)) failure from g++ 11.1.0

[rguenth at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100381

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|11.3|11.4

--- Comment #3 from Richard Biener  ---
GCC 11.3 is being released, retargeting bugs to GCC 11.4.

[Bug libstdc++/100381] [11/12 Regression] new static_assert((std::__is_complete_or_unbounded(...)) failure from g++ 11.1.0

[redi at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100381

--- Comment #2 from Jonathan Wakely  ---
This is almost certainly invalid code. Implementations are not required to
enforce the complete type precondition, so "other compilers don't reject it"
doesn't mean much. If the code has undefined behaviour then it's conforming to
accept it silently, or to reject it like this.

I haven't analyzed it in detail yet though.

[Bug libstdc++/100381] [11/12 Regression] new static_assert((std::__is_complete_or_unbounded(...)) failure from g++ 11.1.0

[rguenth at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100381

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|11.2|11.3

--- Comment #1 from Richard Biener  ---
GCC 11.2 is being released, retargeting bugs to GCC 11.3

[Bug libstdc++/100381] [11/12 Regression] new static_assert((std::__is_complete_or_unbounded(...)) failure from g++ 11.1.0

[rguenth at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100381

Richard Biener  changed:

   What|Removed |Added

   Keywords||rejects-valid
  Component|c++ |libstdc++
   Target Milestone|--- |11.2
Summary|new |[11/12 Regression] new
   |static_assert((std::__is_co |static_assert((std::__is_co
   |mplete_or_unbounded(...))   |mplete_or_unbounded(...))
   |failure from g++ 11.1.0 |failure from g++ 11.1.0