public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105946] [12 Regression] ICE in maybe_warn_pass_by_reference, at tree-ssa-uninit.cc:843 Date: Fri, 15 Jul 2022 11:21:43 +0000 [thread overview] Message-ID: <bug-105946-4-PHWiSvHA3Z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105946-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105946 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marxin at gcc dot gnu.org Keywords|needs-reduction | --- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> --- Reduced to something like: $ cat ice.ii void __throw_bad_array_new_length(); template <typename> void forward(); template <typename> struct __new_allocator { int allocate(long __n, const void * = 0) { if (__builtin_expect(__n, false)) if (__n) __throw_bad_array_new_length(); } }; template <typename> struct allocator_traits; template <typename _Tp> struct allocator_traits<__new_allocator<_Tp>> { using allocator_type = __new_allocator<_Tp>; using pointer = _Tp; using size_type = long; static pointer allocate(allocator_type &__a, size_type __n) { __a.allocate(__n); } }; struct __alloc_traits : allocator_traits<__new_allocator<int>> {}; template <typename, typename, typename, typename, typename = int> struct _Rb_tree { struct _Alloc_node { _Alloc_node(_Rb_tree); template <typename _Arg> void operator()(_Arg) { __new_allocator<int> __trans_tmp_1; __alloc_traits::allocate(__trans_tmp_1, 1); } }; template <typename _Arg, typename _NodeGen> int _M_insert_(int, int, _Arg &&, _NodeGen &); template <typename _Arg> int _M_insert_unique(_Arg &&); }; template <typename _Key, typename _Val, typename _KeyOfValue, typename _Compare, typename _Alloc> template <typename _Arg, typename _NodeGen> int _Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::_M_insert_( int, int, _Arg &&, _NodeGen &__node_gen) { __node_gen(forward<_Arg>); } template <typename _Key, typename _Val, typename _KeyOfValue, typename _Compare, typename _Alloc> template <typename _Arg> int _Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::_M_insert_unique( _Arg &&) { int __res_1, __res_0; _Alloc_node __an(*this); _M_insert_(__res_0, __res_1, forward<_Arg>, __an); } struct set { _Rb_tree<int, int, int, int> _M_t; int insert___x; void insert() { _M_t._M_insert_unique(insert___x); } }; main() { set the_set; the_set.insert(); }
next prev parent reply other threads:[~2022-07-15 11:21 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-13 12:58 [Bug c++/105946] New: [12/13 " gscfq@t-online.de 2022-06-14 9:09 ` [Bug c++/105946] " rguenth at gcc dot gnu.org 2022-06-14 10:53 ` cvs-commit at gcc dot gnu.org 2022-06-14 10:54 ` [Bug c++/105946] [12 " rguenth at gcc dot gnu.org 2022-07-15 11:21 ` marxin at gcc dot gnu.org [this message] 2022-07-19 11:37 ` cvs-commit at gcc dot gnu.org 2022-07-19 11:38 ` rguenth 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-105946-4-PHWiSvHA3Z@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: linkBe 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).