public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: dominique.devriese@student.kuleuven.ac.be, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/10858: failure with calling a method inside sizeof: sorry, unimplemented: `method_call_expr' not supported by dump_expr Date: Tue, 20 May 2003 01:02:00 -0000 [thread overview] Message-ID: <20030520010232.25841.qmail@sources.redhat.com> (raw) Old Synopsis: bogus compiler failure while compiling Boost.Python New Synopsis: failure with calling a method inside sizeof: sorry, unimplemented: `method_call_expr' not supported by dump_expr State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Tue May 20 01:02:32 2003 State-Changed-Why: Confirmed. Here's a much smaller snippet: ---------------------- template <int> struct P {}; void bar (); template <class T> struct X { static int foo(void (*)()); P<sizeof(foo(&bar))> p; }; template class X<int>; -------------------------- With 3.3, we presently get: g/x> /home/bangerth/bin/gcc-3.3-pre/bin/g++ -c x.cc x.cc:7: sorry, unimplemented: `method_call_expr' not supported by dump_expr x.cc:7: sorry, unimplemented: `method_call_expr' not supported by dump_expr With 3.4, this code doesn't go through the parser (which is reported elsewhere), so it's hard to tell whether the problem is fixed there. Here's what present mainline gives us: g/x> /home/bangerth/bin/gcc-3.4-pre/bin/g++ -c x.cc x.cc: In instantiation of `X<int>': x.cc:10: instantiated from here x.cc:7: error: invalid use of undefined type `struct X<int>' x.cc:5: error: declaration of `struct X<int>' Working around the problem in 3.4 by using X::foo makes the problem go away in 3.3 and 3.4. I tend to think, though, that this is indeed valid code and that it should be accepted in any case. W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10858
reply other threads:[~2003-05-20 1:02 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030520010232.25841.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=dominique.devriese@student.kuleuven.ac.be \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).