public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108047] ice: unexpected expression of kind implicit_conv_expr
Date: Mon, 12 Dec 2022 12:06:14 +0000	[thread overview]
Message-ID: <bug-108047-4-kMbfFd9FXu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108047-4@http.gcc.gnu.org/bugzilla/>

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

Sergei Trofimovich <slyfox at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |slyfox at gcc dot gnu.org

--- Comment #4 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
Noticed the same build failure on this week's gcc on apache-arrow-cpp-9.0.0.
Extracted small example:

namespace std {
template <class> class initializer_list;
struct Trans_NS___cxx11_basic_string {
  Trans_NS___cxx11_basic_string(const char *);
};
struct vector {
  vector(initializer_list<Trans_NS___cxx11_basic_string>);
};
} // namespace std
void key_value_metadata(std::vector, std::vector);
template <class> void TestWriteDifferentMetadata() {
  key_value_metadata({}, {""});
}

Not sure if it's valid, but gcc-12 still accepts it. Can re-reduce against
clang if needed.

$ ./gcc-git/bin/gcc  -c bug.cc.cc
bug.cc.cc: In function 'void TestWriteDifferentMetadata()':
bug.cc.cc:12:21: internal compiler error: unexpected expression
'(std::Trans_NS___cxx11_basic_string)""' of kind implicit_conv_expr
   12 |   key_value_metadata({}, {""});
      |   ~~~~~~~~~~~~~~~~~~^~~~~~~~~~
0x219cf54 diagnostic_impl(rich_location*, diagnostic_metadata const*, int, char
const*, __va_list_tag (*) [1], diagnostic_t)
        ???:0
0x219dba6 internal_error(char const*, ...)
        ???:0
0x9d4fee cxx_eval_constant_expression(constexpr_ctx const*, tree_node*,
value_cat, bool*, bool*, tree_node**)
        ???:0

  parent reply	other threads:[~2022-12-12 12:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10 11:38 [Bug c++/108047] New: " dcb314 at hotmail dot com
2022-12-11  8:32 ` [Bug c++/108047] " dcb314 at hotmail dot com
2022-12-11  8:57 ` dcb314 at hotmail dot com
2022-12-11  9:26 ` dcb314 at hotmail dot com
2022-12-12 12:06 ` slyfox at gcc dot gnu.org [this message]
2022-12-12 13:22 ` [Bug c++/108047] [13 Regression] ICE: unexpected expression of kind implicit_conv_expr since r13-4564-gd081807d8d70e3e8 marxin at gcc dot gnu.org
2022-12-12 16:39 ` pinskia at gcc dot gnu.org
2022-12-21 11:45 ` rguenth at gcc dot gnu.org
2022-12-21 22:19 ` slyfox at gcc dot gnu.org
2023-01-02 16:41 ` pinskia at gcc dot gnu.org
2023-01-06 11:20 ` jakub at gcc dot gnu.org
2023-01-06 18:50 ` pinskia at gcc dot gnu.org
2023-01-06 20:06 ` slyfox at gcc dot gnu.org
2023-01-09 22:41 ` cvs-commit at gcc dot gnu.org
2023-01-23 15:41 ` mpolacek at gcc dot gnu.org
2023-01-23 15:45 ` jakub 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-108047-4-kMbfFd9FXu@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).