public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Meenaradchagan Vishnu <mvishnu@fla.fujitsu.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9575: Internal compiler error in resolve_offset_ref, at cp/init.c: 1886 Date: Wed, 05 Feb 2003 00:06:00 -0000 [thread overview] Message-ID: <20030205000600.18178.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9575; it has been noted by GNATS. From: Meenaradchagan Vishnu <mvishnu@fla.fujitsu.com> To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mvishnu@fla.fujitsu.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c++/9575: Internal compiler error in resolve_offset_ref, at cp/init.c: 1886 Date: Tue, 4 Feb 2003 16:02:06 -0800 (PST) Hi, Thank you very much for your prompt response. Is the restriction on paranthesis use conforms to the C++ standards? Note that this code compiles and works as intended on other compilers. Sincerely, Meenan Vishnu >Date: 4 Feb 2003 23:35:37 -0000 >To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mvishnu@fla.fujitsu.com, nobody@gcc.gnu.org >From: bangerth@dealii.org >Subject: Re: c++/9575: Internal compiler error in resolve_offset_ref, at cp/init.c: 1886 > >Synopsis: Internal compiler error in resolve_offset_ref, at cp/init.c: 1886 > >State-Changed-From-To: open->closed >State-Changed-By: bangerth >State-Changed-When: Tue Feb 4 23:35:37 2003 >State-Changed-Why: > Confirmed with 3.2, but already fixed in 3.2.2pre, 3.3 and > 3.4: > > mp/g> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc > x.cc: In function `void func(foo*)': > x.cc:16: error: parenthesis around 'foo::operator&=(const foo&)' cannot be used > to form a pointer-to-member-function > >http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9 575
next reply other threads:[~2003-02-05 0:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-05 0:06 Meenaradchagan Vishnu [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-05 0:16 Wolfgang Bangerth 2003-02-04 23:35 bangerth 2003-02-04 23:26 mvishnu
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=20030205000600.18178.qmail@sources.redhat.com \ --to=mvishnu@fla.fujitsu.com \ --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).