public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108773] [13 Regression] ICE in gimplify_var_or_parm_decl, at gimplify.cc:3058 compiling ceph since r13-4563-g1e1847612d7f169f
Date: Mon, 13 Feb 2023 17:06:14 +0000	[thread overview]
Message-ID: <bug-108773-4-ac5Gjt4DHn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108773-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Slightly better testcase where basic_string, array and list are at least
templates, again -std=c++20:

namespace std {
struct __new_allocator {};
template <typename> using __allocator_base = __new_allocator;
struct allocator : __allocator_base<int> {};
template <class> struct initializer_list {
  void *_M_array;
  decltype(sizeof 0) __rebind;
};
template <typename T>
struct basic_string {
  basic_string(const T *, allocator = allocator());
  ~basic_string();
};
using string = basic_string<char>;
template <typename T>
struct array {
  T _M_elems;
};
template <typename T>
struct list {
  list &operator=(initializer_list<T>);
};
}
struct RGWSyncTraceManager {
  std::list<std::array<std::string>> admin_commands;
  void hook_to_admin_command();
};
void RGWSyncTraceManager::hook_to_admin_command() {
  admin_commands = {{""}, {""}};
}

  parent reply	other threads:[~2023-02-13 17:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 12:54 [Bug c++/108773] New: internal compiler error: in gimplify_var_or_parm_decl, at gimplify.cc:3058 compiling ceph kkeithle at redhat dot com
2023-02-13 13:04 ` [Bug c++/108773] " kkeithle at redhat dot com
2023-02-13 13:05 ` marxin at gcc dot gnu.org
2023-02-13 13:16 ` [Bug c++/108773] [13 Regression] ICE in gimplify_var_or_parm_decl, at gimplify.cc:3058 compiling ceph since r13-4563-g1e1847612d7f169f marxin at gcc dot gnu.org
2023-02-13 13:18 ` marxin at gcc dot gnu.org
2023-02-13 13:27 ` jakub at gcc dot gnu.org
2023-02-13 14:27 ` jakub at gcc dot gnu.org
2023-02-13 14:39 ` jakub at gcc dot gnu.org
2023-02-13 15:54 ` jakub at gcc dot gnu.org
2023-02-13 16:03 ` marxin at gcc dot gnu.org
2023-02-13 16:11 ` jakub at gcc dot gnu.org
2023-02-13 17:06 ` jakub at gcc dot gnu.org [this message]
2023-02-13 17:07 ` jakub at gcc dot gnu.org
2023-02-27 10:33 ` rguenth at gcc dot gnu.org
2023-03-07  3:01 ` jason at gcc dot gnu.org
2023-03-08  3:35 ` jason at gcc dot gnu.org
2023-03-09 21:26 ` cvs-commit at gcc dot gnu.org
2023-03-09 21:30 ` jason at gcc dot gnu.org
2023-03-13 18:07 ` kkeithle at redhat dot com

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-108773-4-ac5Gjt4DHn@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).