This is the mail archive of the gcc-prs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: c++/7807: g++ 3.2 Fails to compile legal code that compiled OKwith g++ 3.1


The following reply was made to PR c++/7807; it has been noted by GNATS.

From: Anthony Williams <anthony_w@onetel.net.uk>
To: Andris Pavenis <pavenis@lanet.lv>
Cc: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, anthony@anthonyw.cjb.net,
        gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: c++/7807: g++ 3.2 Fails to compile legal code that compiled OKwith g++ 3.1
Date: Mon, 2 Sep 2002 16:07:08 +0100

 >Date: Mon, 02 Sep 2002 17:56:30 +0300
 >From: Andris Pavenis <pavenis@lanet.lv>  
 
 >Looks the same as PR#7648 I reported about 2 weeks ago (for
 i386-slackware-linux and
 >i586-pc-msdosdjgpp).
 >
 >http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7648
 
 It's certainly similar and therefore probably related --- in your case, it is
 the member function pointer itself that is being initialized, and which draws
 the complaint. In my case, the presence of a member that is a union which
 contains a member function pointer causes the compiler to complain about the
 initialization of the _other_ members.
 
 Anthony


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]