From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18199 invoked by alias); 5 Feb 2003 00:06:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 18179 invoked by uid 71); 5 Feb 2003 00:06:00 -0000 Date: Wed, 05 Feb 2003 00:06:00 -0000 Message-ID: <20030205000600.18178.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Meenaradchagan Vishnu Subject: Re: c++/9575: Internal compiler error in resolve_offset_ref, at cp/init.c: 1886 Reply-To: Meenaradchagan Vishnu X-SW-Source: 2003-02/txt/msg00240.txt.bz2 List-Id: The following reply was made to PR c++/9575; it has been noted by GNATS. From: Meenaradchagan Vishnu 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