public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ldalessandro at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/109751] New: boost interface_interface fails concept check starting in gcc-13
Date: Fri, 05 May 2023 17:45:48 +0000	[thread overview]
Message-ID: <bug-109751-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109751
           Summary: boost interface_interface fails concept check starting
                    in gcc-13
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ldalessandro at gmail dot com
  Target Milestone: ---

The following example is reduced from
https://github.com/boostorg/stl_interfaces/blob/boost-1.82.0/example/node_iterator.cpp.
It compiles fine in gcc-12 but fails a concept check in gcc-13.


  #include <boost/stl_interfaces/iterator_interface.hpp>

  template<typename T>
  struct iterator : boost::stl_interfaces::iterator_interface<iterator<T>, 
  std::forward_iterator_tag, T>
  {
    using base_type = boost::stl_interfaces::iterator_interface<iterator<T>,
std::forward_iterator_tag, T>;
    using base_type::operator++;

    T& operator*() const;
    iterator& operator++();
    bool operator==(iterator) const;
  };

  static_assert(std::incrementable<iterator<int>>);

Live: https://godbolt.org/z/6qsx1narj

The error tells us that this requires clause changes from false to true.

      friend constexpr bool operator<(D lhs, D rhs)
        requires std::equality_comparable<D> {
          return (lhs - rhs) < typename D::difference_type(0);
        }

https://github.com/boostorg/stl_interfaces/blob/boost-1.82.0/include/boost/stl_interfaces/iterator_interface.hpp#L779

I don't think that requires clause makes any sense, but I also don't know why
the behavior would have changed from gcc-12 to gcc-13.

             reply	other threads:[~2023-05-05 17:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05 17:45 ldalessandro at gmail dot com [this message]
2023-05-05 17:50 ` [Bug c++/109751] boost iterator_interface " pinskia at gcc dot gnu.org
2023-05-05 17:59 ` ldalessandro at gmail dot com
2023-05-05 18:06 ` ldalessandro at gmail dot com
2023-05-05 18:09 ` pinskia at gcc dot gnu.org
2023-05-05 18:11 ` ldalessandro at gmail dot com
2023-05-05 18:14 ` pinskia at gcc dot gnu.org
2023-05-05 18:41 ` pinskia at gcc dot gnu.org
2023-05-05 18:54 ` ldalessandro at gmail dot com
2023-05-05 19:00 ` pinskia at gcc dot gnu.org
2023-05-05 19:24 ` pinskia at gcc dot gnu.org
2023-05-05 20:01 ` pinskia at gcc dot gnu.org
2023-05-05 20:02 ` pinskia at gcc dot gnu.org
2023-05-06 22:02 ` redi at gcc dot gnu.org
2023-05-06 22:05 ` redi at gcc dot gnu.org
2023-05-06 23:28 ` ldalessandro at gmail dot com
2023-05-08 15:46 ` ldalessandro at gmail dot com
2023-05-08 16:00 ` redi at gcc dot gnu.org
2023-05-09 19:20 ` ppalka at gcc dot gnu.org
2023-05-09 21:24 ` [Bug c++/109751] [13/14 Regression] " ppalka at gcc dot gnu.org
2023-05-09 21:27 ` ppalka at gcc dot gnu.org
2023-05-10 19:10 ` ppalka at gcc dot gnu.org
2023-07-21 14:09 ` ppalka at gcc dot gnu.org
2023-07-27  9:26 ` rguenth at gcc dot gnu.org
2023-08-17 15:52 ` jason at gcc dot gnu.org
2023-08-22 18:36 ` cvs-commit at gcc dot gnu.org
2023-08-31 22:40 ` cvs-commit at gcc dot gnu.org
2023-08-31 22:40 ` jason at gcc dot gnu.org
2023-10-16 18:33 ` ppalka at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-109751-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).