public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104184] [11/12 Regression] ICE Error reporting routines re-entered. xref_basetypes
Date: Sat, 22 Jan 2022 11:14:17 +0000	[thread overview]
Message-ID: <bug-104184-4-gGVLHMkTFQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104184-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
A different reduction from the same code. This one does not compile with clang
anymore. ICEs with -Wall -W, but not if I remove one of them.

using mp_false = struct mp_identity { using type = void; };
template <bool, class T> using mp_if_c = typename T ::type;
template <class L, long I> using mp_at_c = typename mp_if_c<I, L>::type;
template <typename List, typename, typename> using make_arg_list = List;
template <typename SpecSeq> using make_parameter_spec_items = SpecSeq;
template <typename Parameters> struct argument_pack {
  using type =
      mp_at_c<typename make_arg_list<
                  typename make_parameter_spec_items<
                      typename Parameters::parameter_spec>::type,
                  typename Parameters::deduced_listboosttag_keyword_arg,
                  mp_false>::type,
              0>;
};
void no_exude();
template <typename> using boost_param_result_465refine_mesh_3 = mp_identity;
template <typename ParameterArgumentType0, typename ParameterArgumentType1,
          typename ParameterArgumentType2, typename ParameterArgumentType3,
          typename ParameterArgumentType4, typename ParameterArgumentType5>
typename boost_param_result_465refine_mesh_3<
    typename argument_pack<ParameterArgumentType5>::type>::type
refine_mesh_3(ParameterArgumentType0, ParameterArgumentType1,
              ParameterArgumentType2, ParameterArgumentType3,
              ParameterArgumentType4, ParameterArgumentType5 a5) {}
int verify___trans_tmp_1, image_domain;
struct Tester {
  template <typename C3t3, typename Domain, typename Criteria,
            typename Domain_type_tag>
  void verify(C3t3 c3t3, Domain domain, Criteria criteria, Domain_type_tag) {
    refine_mesh_3(c3t3, domain, criteria, no_exude, verify___trans_tmp_1,
                  verify___trans_tmp_1);
  }
} image_c3t3;
struct Image_tester : Tester {
  void image() {
    void criteria();
    verify(image_c3t3, image_domain, criteria, int());
  }
};

  reply	other threads:[~2022-01-22 11:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-22 11:11 [Bug c++/104184] New: " glisse at gcc dot gnu.org
2022-01-22 11:14 ` glisse at gcc dot gnu.org [this message]
2022-01-22 11:19 ` [Bug c++/104184] " glisse at gcc dot gnu.org
2022-01-22 11:37 ` pinskia at gcc dot gnu.org
2022-01-22 23:13 ` glisse at gcc dot gnu.org
2022-01-22 23:30 ` glisse at gcc dot gnu.org
2022-01-24  8:10 ` [Bug c++/104184] [11/12 Regression] ICE Error reporting routines re-entered. xref_basetypes since r11-291-g0f50f6daa140186a marxin at gcc dot gnu.org
2022-01-24  8:16 ` pinskia at gcc dot gnu.org
2022-01-24  9:12 ` rguenth at gcc dot gnu.org
2022-01-26  5:01 ` 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-104184-4-gGVLHMkTFQ@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).