From: David Krauss <potswa@mac.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] [Bug c++/49118] fake template nesting for operator-> chain
Date: Fri, 10 Jun 2011 03:29:00 -0000 [thread overview]
Message-ID: <55A50BA6-CB3B-4A36-A4A7-F6E1747C4F32@mac.com> (raw)
In-Reply-To: <4DF1874B.4030708@redhat.com>
On Jun 9, 2011, at 7:54 PM, Jason Merrill wrote:
> Looks good, just need ChangeLog and testcase now.
>
> Jason
The changelog is the .clog attachment to previous.
I tried the testcase below but dejagnu seemed to hang with no compiler process running. I really don't know how to use dg, so perhaps there's an obvious error.
- D
// { dg-do compile }
template< int n >
struct a {
a< n+1 >
operator->()
{ return a< n+1 >(); }
};
int main() {
a<0>()->x; // { dg-error "instantiation depth exceeds maximum" }
}
next prev parent reply other threads:[~2011-06-10 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-49118-18186@http.gcc.gnu.org/bugzilla/>
[not found] ` <bug-49118-18186-fnN8jlsJie@http.gcc.gnu.org/bugzilla/>
2011-06-02 19:26 ` David Krauss
2011-06-06 20:28 ` Jason Merrill
2011-06-09 23:43 ` David Krauss
2011-06-10 3:00 ` Jason Merrill
2011-06-10 3:29 ` David Krauss [this message]
2011-06-10 6:50 ` Jason Merrill
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=55A50BA6-CB3B-4A36-A4A7-F6E1747C4F32@mac.com \
--to=potswa@mac.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
/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).