Re: C++ PATCH for c++/55877 (names for linkage purposes)

2014-03-03 Thread Jakub Jelinek
On Mon, Mar 03, 2014 at 04:49:24PM +0100, Dominique Dhumieres wrote: > The test g++.dg/abi/anon2.C introduced at r208157 causes: > > UNRESOLVED: g++.dg/abi/anon2.C -std=c++98 scan-assembler > .weak(_definition)?[ \\t]_?_ZN2N11D1C3fn1ENS0_1BE > UNRESOLVED: g++.dg/abi/anon2.C -std=c++98 scan-asse

Re: C++ PATCH for c++/55877 (names for linkage purposes)

2014-03-03 Thread Dominique Dhumieres
The test g++.dg/abi/anon2.C introduced at r208157 causes: UNRESOLVED: g++.dg/abi/anon2.C -std=c++98 scan-assembler .weak(_definition)?[ \\t]_?_ZN2N11D1C3fn1ENS0_1BE UNRESOLVED: g++.dg/abi/anon2.C -std=c++98 scan-assembler .weak(_definition)?[ \\t]_?_ZN2N11D1C3fn2ES1_ UNRESOLVED: g++.dg/abi/ano

C++ PATCH for c++/55877 (names for linkage purposes)

2014-02-25 Thread Jason Merrill
My earlier patch didn't go far enough; when we apply a name for linkage purposes and fix up the visibility of the type, we also need to fix up the visibility and names of any members and implementation bits. At first I thought we would need to deal with static data members as well as functions