public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "erich.keane at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/94203] New: experimental/executor and socket header issues-
Date: Tue, 17 Mar 2020 16:16:33 +0000	[thread overview]
Message-ID: <bug-94203-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 94203
           Summary: experimental/executor and socket header issues-
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: erich.keane at intel dot com
  Target Milestone: ---

Again detected by trying to compile these headers with clang, I get two more
issues.  They can be reproduced here: https://godbolt.org/z/L-UVGq though that
still shows the previous version's issue with service_already_exists.

First, it appears that _TgtImpl attempts to add 'const' to the return type of
the overridden function:

../include/c++/10.0.1/experimental/executor:1170:2: error:
      return type of virtual function 'target' is not covariant with the return
type of the function it overrides (class type
      'const void *' is more qualified than class type 'void *'
        target(const std::type_info& __ti) const
        ^
../include/c++/10.0.1/experimental/executor:1138:21: note:
      overridden virtual function is here
      virtual void* target(const std::type_info&) const = 0;




The second issue is that socket_errc doesn't pass is_error_code_enum in
__basic_socket_impl:

../include/c++/10.0.1/experimental/socket:571:9: error:
      no viable overloaded '='
          __ec = socket_errc::already_open;
          ~~~~ ^ ~~~~~~~~~~~~~~~~~~~~~~~~~
../include/c++/10.0.1/system_error:208:7: note:
      candidate template ignored: requirement
'is_error_code_enum<std::experimental::net::v1::socket_errc>::value' was not
      satisfied [with _ErrorCodeEnum = std::experimental::net::v1::socket_errc]
      operator=(_ErrorCodeEnum __e) noexcept
      ^

(it then goes on to show a bunch of other options).

However, I believe this is because Clang is instantiating this check right
away, but the explicit specialization for socket_errc is after it:
https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-v3/include/experimental/socket#L2605


In fact, clang diagnoses this as well:

../include/c++/10.0.1/experimental/socket:2606:12: error:
      explicit specialization of
'std::is_error_code_enum<std::experimental::net::v1::socket_errc>' after
instantiation
    struct is_error_code_enum<experimental::net::v1::socket_errc>
           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../include/c++/10.0.1/system_error:206:26: note:
      implicit instantiation first required here
      typename enable_if<is_error_code_enum<_ErrorCodeEnum>::value,
                         ^

             reply	other threads:[~2020-03-17 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17 16:16 erich.keane at intel dot com [this message]
2020-03-17 16:53 ` [Bug libstdc++/94203] " redi at gcc dot gnu.org
2020-03-18  0:23 ` cvs-commit at gcc dot gnu.org
2020-04-24 13:07 ` redi at gcc dot gnu.org
2020-04-24 13:32 ` cvs-commit at gcc dot gnu.org
2020-04-24 13:32 ` redi 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-94203-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).