public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110552] ICE on valid code in maybe_instantiate_noexcept
Date: Tue, 04 Jul 2023 21:28:16 +0000	[thread overview]
Message-ID: <bug-110552-4-H2H1cG48Fa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110552-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Created attachment 55470
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55470&action=edit
reduced but invalid code

This is the reduced testcase I got but it became invalid code; maybe the
original is invalid too. But clang's error message is:
<source>:31:25: error: member reference base type '__tag_t' (aka 'void') is not
a structure or union
   31 |       noexcept(__tag_t().get_env(__self))) {}
      |                ~~~~~~~~~^~~~~~~~
<source>:30:15: note: in instantiation of exception specification for
'tag_invoke<stdexec::__env::get_env_t, stdexec::__basic_sender<stdexec::(lambda
at <source>:33:25)>>' requested here
   30 |   friend auto tag_invoke(_Tag, const _Self &__self) noexcept(
      |               ^
<source>:6:14: note: in instantiation of function template specialization
'stdexec::tag_invoke<stdexec::__env::get_env_t,
stdexec::__basic_sender<stdexec::(lambda at <source>:33:25)>>' requested here
    6 |     decltype(tag_invoke(__declval<_Tag>(), __declval<_Args>()...));
      |              ^
<source>:13:10: note: in instantiation of template type alias
'tag_invoke_result_t' requested here
   13 |       -> tag_invoke_result_t<get_env_t, const _EnvProvider &> {}
      |          ^
<source>:19:36: note: while substituting deduced template arguments into
function template 'operator()' [with _EnvProvider =
stdexec::__basic_sender<stdexec::(lambda at <source>:33:25)>]
   19 |                                  { get_env(__ep) };
      |                                    ^
<source>:19:36: note: in instantiation of requirement here
   19 |                                  { get_env(__ep) };
      |                                    ^~~~~~~~~~~~~
<source>:18:32: note: while substituting template arguments into constraint
expression here
   18 | concept environment_provider = requires(_EnvProvider &__ep) {
      |                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   19 |                                  { get_env(__ep) };
      |                                  ~~~~~~~~~~~~~~~~~~
   20 |                                };
      |                                ~
<source>:35:15: note: while checking the satisfaction of concept
'environment_provider<stdexec::__basic_sender<stdexec::(lambda at
<source>:33:25)>>' requested here
   35 | static_assert(stdexec::environment_provider<S>);
      |               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  parent reply	other threads:[~2023-07-04 21:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 18:07 [Bug c++/110552] New: " eric.niebler at gmail dot com
2023-07-04 18:49 ` [Bug c++/110552] " pinskia at gcc dot gnu.org
2023-07-04 21:13 ` pinskia at gcc dot gnu.org
2023-07-04 21:28 ` pinskia at gcc dot gnu.org [this message]
2023-07-04 21:30 ` pinskia at gcc dot gnu.org
2023-07-04 21:30 ` pinskia at gcc dot gnu.org
2023-07-04 21:36 ` pinskia at gcc dot gnu.org
2024-04-13  8:25 ` pinskia 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-110552-4-H2H1cG48Fa@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).