This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/37170] [4.4 Regression]: gcc.dg/weak/weak-1.c
- From: "dominiq at lps dot ens dot fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 25 Aug 2008 18:12:43 -0000
- Subject: [Bug middle-end/37170] [4.4 Regression]: gcc.dg/weak/weak-1.c
- References: <bug-37170-507@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #47 from dominiq at lps dot ens dot fr 2008-08-25 18:12 -------
> To help shorten the number of iterations, can you please verify that the
> failures all look as above in the .log files?
You have to realize that I am C* illiterate. So I need more precise directives.
For instance, do
...
class Barf : virtual public Bar {
public:
virtual void init(int argc, char **argv) { Bar::init(argc, argv); }
};
...
[ibook-dhum] f90/bug% g++44
/opt/gcc/_gcc_clean/gcc/testsuite/g++.old-deja/g++.mike/offset1.C/var/tmp//ccIY8j6p.s:unknown:Undefined
symbol: __ZTV4Barf can't be a weak_definition
and
...
struct B : virtual A
{
virtual int f() { return 1; }
virtual int g() = 0;
};
...
[ibook-dhum] f90/bug% g++44 -c
/opt/gcc/_gcc_clean/gcc/testsuite/g++.old-deja/g++.brendan/misc11.C
/var/tmp//cccB5iE4.s:unknown:Undefined symbol: __ZTV1B can't be a
weak_definition
look the same? My answer is "yes", but in the first case the symbol is a class
and in the second one a struct(ure?), so the "yes" may be a mistake.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37170