public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107267] ice in cp_gimplify_init_expr, at cp/cp-gimplify.cc:253
Date: Sat, 15 Oct 2022 11:00:37 +0000	[thread overview]
Message-ID: <bug-107267-4-sRhjqkCkWE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107267-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from David Binderman <dcb314 at hotmail dot com> ---
Reduced C++ code is

template <int __v> struct integral_constant {
  static constexpr int value = __v;
};
template <bool __v> using __bool_constant = integral_constant<__v>;
template <int> struct __conditional {
  template <typename _Tp, typename> using type = _Tp;
};
template <bool _Cond, typename _If, typename _Else>
using __conditional_t = typename __conditional<_Cond>::type<_If, _Else>;
template <typename _Tp> struct remove_reference { using type = _Tp; };
namespace std {
template <typename _Tp> typename remove_reference<_Tp>::type &&move(_Tp &&);
struct pair {
  int second;
};
template <int _Constant_iterators> struct _Hashtable_traits {
  using __constant_iterators = __bool_constant<_Constant_iterators>;
};
template <int __constant_iterators> struct _Node_iterator {
  using value_type = pair;
  using pointer =
      __conditional_t<__constant_iterators, value_type *, value_type>;
  pointer operator->();
};
struct _Insert_base {
  using __constant_iterators = _Hashtable_traits<false>::__constant_iterators;
  using iterator = _Node_iterator<__constant_iterators::value>;
};
template <typename, typename> using __umap_hashtable = _Insert_base;
struct unordered_map {
  __umap_hashtable<int, int>::iterator find(int);
};
} // namespace std
template <typename, typename> using unordered_map = std::unordered_map;
struct vl_concurrent_unordered_map {
  struct FindResult {
    FindResult(bool, int);
    std::pair result;
  };
  int pop_key;
  void pop() {
    auto itr = maps[0].find(pop_key);
    auto ret = std::move(FindResult(true, itr->second));
  }
  unordered_map<int, int> maps[];
} unique_id_mapping;
void DispatchDestroyAccelerationStructureKHR() { unique_id_mapping.pop(); }

  parent reply	other threads:[~2022-10-15 11:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 16:18 [Bug c++/107267] New: " dcb314 at hotmail dot com
2022-10-14 16:25 ` [Bug c++/107267] " dcb314 at hotmail dot com
2022-10-14 16:29 ` dcb314 at hotmail dot com
2022-10-15 11:00 ` dcb314 at hotmail dot com [this message]
2022-10-16  6:39 ` dcb314 at hotmail dot com
2022-10-16  7:03 ` dcb314 at hotmail dot com
2022-10-16  7:21 ` dcb314 at hotmail dot com
2022-10-16  7:30 ` dcb314 at hotmail dot com
2022-10-17 11:31 ` [Bug c++/107267] [13 Regression] ICE in cp_gimplify_init_expr, at cp/cp-gimplify.cc:253 since r13-3175-g6ffbf87ca66f4ed9 marxin at gcc dot gnu.org
2022-10-17 11:32 ` marxin at gcc dot gnu.org
2022-10-17 11:35 ` marxin at gcc dot gnu.org
2022-10-17 11:35 ` marxin at gcc dot gnu.org
2022-10-20 18:39 ` dcb314 at hotmail dot com
2022-10-20 18:52 ` ppalka at gcc dot gnu.org
2023-01-23 22:04 ` jason at gcc dot gnu.org
2023-01-23 23:35 ` cvs-commit at gcc dot gnu.org
2023-01-24  2:53 ` jason 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-107267-4-sRhjqkCkWE@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).