public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100409] C++ FE elides pure throwing call Date: Thu, 08 Jul 2021 08:38:21 +0000 [thread overview] Message-ID: <bug-100409-4-eXs533Kw53@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100409-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100409 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Hmm, doesn't quite work. FAIL: g++.dg/cpp0x/sfinae19.C -std=c++14 (internal compiler error) FAIL: g++.dg/cpp0x/sfinae22.C -std=c++14 (internal compiler error) FAIL: g++.dg/cpp1y/pr61636-2.C -std=c++14 (internal compiler error) FAIL: g++.dg/warn/noeffect4.C -std=gnu++14 (test for errors, line 79) FAIL: g++.dg/warn/noeffect4.C -std=gnu++14 (test for warnings, line 80) FAIL: g++.dg/warn/noeffect4.C -std=gnu++14 (test for warnings, line 82) FAIL: g++.dg/warn/noeffect4.C -std=gnu++14 (test for warnings, line 83) FAIL: g++.dg/warn/noeffect4.C -std=gnu++14 (test for warnings, line 84) FAIL: g++.dg/warn/noeffect4.C -std=gnu++14 (test for warnings, line 85) FAIL: g++.dg/warn/noeffect4.C -std=gnu++14 (test for warnings, line 88) FAIL: g++.dg/warn/noeffect4.C -std=gnu++14 (internal compiler error) FAIL: g++.dg/warn/noeffect4.C -std=gnu++14 (test for excess errors) the ICE is /home/rguenther/src/trunk/gcc/testsuite/g++.dg/cpp0x/sfinae19.C:8:30: internal compiler error: in check_noexcept_r, at cp/except.c:1053^M if ((code == CALL_EXPR && CALL_EXPR_FN (t)) || code == AGGR_INIT_EXPR) { /* We can only use the exception specification of the called function for determining the value of a noexcept expression; we can't use TREE_NOTHROW, as it might have a different value in another translation unit, creating ODR problems. We could use TREE_NOTHROW (t) for !TREE_PUBLIC fns, though... */ tree fn = cp_get_callee (t); if (concept_check_p (fn)) return NULL_TREE; tree type = TREE_TYPE (fn); gcc_assert (INDIRECT_TYPE_P (type)); where the type is likely the lang_type in: <call_expr 0x7ffff65504d0 fn <component_ref 0x7ffff66b34e0 type <lang_type 0x7ffff66851f8 unknown type type <lang_type 0x7ffff66851f8 unknown type> VOID align:1 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type 0x7ffff66851f8 pointer_to_this <lang_type 0x7ffff66851f8 unknown type> reference_to_this <lang_type 0x7ffff66851f8 unknown type>> whatever that exactly is, it isn't a reference or pointer type. processing_template_decl is true in this context, but if we assume that in this context expr_noexcept_p is true we probably miss diagnostics. Jason, any idea?
next prev parent reply other threads:[~2021-07-08 8:38 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-04 6:45 [Bug c++/100409] New: " rguenth at gcc dot gnu.org 2021-05-04 6:46 ` [Bug c++/100409] " rguenth at gcc dot gnu.org 2021-05-05 8:02 ` rguenth at gcc dot gnu.org 2021-07-08 7:25 ` rguenth at gcc dot gnu.org 2021-07-08 8:19 ` harald at gigawatt dot nl 2021-07-08 8:38 ` rguenth at gcc dot gnu.org [this message] 2021-07-08 8:38 ` rguenth at gcc dot gnu.org 2021-07-08 8:39 ` rguenth at gcc dot gnu.org 2021-07-08 8:44 ` rguenth at gcc dot gnu.org 2021-07-08 9:17 ` harald at gigawatt dot nl 2021-07-08 9:20 ` rguenth at gcc dot gnu.org 2021-07-08 9:41 ` rguenth at gcc dot gnu.org 2021-07-08 13:15 ` mpolacek at gcc dot gnu.org 2021-07-08 13:53 ` jason at gcc dot gnu.org 2021-07-08 14:09 ` rguenth at gcc dot gnu.org 2021-07-08 15:13 ` jason at gcc dot gnu.org 2021-07-08 22:06 ` mpolacek at gcc dot gnu.org 2022-01-05 14:41 ` 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-100409-4-eXs533Kw53@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).