public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/14355] [3.4/3.5 Regression] ICE in cxx_incomplete_type_diagnostic Date: Tue, 02 Mar 2004 02:24:00 -0000 [thread overview] Message-ID: <20040302022443.23726.qmail@sources.redhat.com> (raw) In-Reply-To: <20040301062119.14355.bangerth@dealii.org> ------- Additional Comments From giovannibajo at libero dot it 2004-03-02 02:24 ------- Mark, I analyzed this. cxx_incomplete_type_diagnostic was ICEing because it was never supposed to get a typename_type (it must have resolved before). You fixed the real bug in PR14377. The only reason why I was keeping this around is to add some checking code to tsubst_build_and_copy (case CALL_EXPR) so that it would check valid incoming call expressions (to catch problems earlier). For instance, there is a piece of code there which seems cut & pasted from the parser, and you just modified it: if (koenig_p && (is_overloaded_fn (function) || DECL_P (function) || TREE_CODE (function) == IDENTIFIER_NODE)) function = perform_koenig_lookup (function, call_args); The problem is, I don't follow the code well enough to add checking to it. So, it doesn't really matter. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |mmitchel at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14355
next prev parent reply other threads:[~2004-03-02 2:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-01 6:21 [Bug c++/14355] New: " bangerth at dealii dot org 2004-03-01 6:21 ` [Bug c++/14355] " bangerth at dealii dot org 2004-03-01 6:39 ` pinskia at gcc dot gnu dot org 2004-03-02 2:13 ` mmitchel at gcc dot gnu dot org 2004-03-02 2:24 ` giovannibajo at libero dot it [this message] 2004-03-02 2:54 ` bangerth at dealii dot org 2004-03-02 3:28 ` mark at codesourcery dot com 2004-03-02 3:33 ` bangerth at dealii dot 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=20040302022443.23726.qmail@sources.redhat.com \ --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).