These new FAILs have been appearing on trunk since some time between 20090820 and 20090903:
FAIL: g++.dg/ext/dllexport-MI1.C scan-assembler -export:_ZNK2D12vfEv FAIL: g++.dg/ext/dllexport-MI1.C scan-assembler -export:_ZNK2D22vfEv FAIL: g++.dg/ext/dllexport-MI1.C scan-assembler -export:_ZNK3MI12vfEv FAIL: g++.dg/ext/dllexport-MI1.C scan-assembler -export:_ZTV2D1,data FAIL: g++.dg/ext/dllexport-MI1.C scan-assembler -export:_ZN2D2C2ERKS_ FAIL: g++.dg/ext/dllexport1.C scan-assembler -export:_ZN3Bar10inline_barEi (Refs: http://gcc.gnu.org/ml/gcc-testresults/2009-08/msg02276.html http://gcc.gnu.org/ml/gcc-testresults/2009-09/msg00356.html ) They seem to represent serious breakage of dllexport with cygwin as the latest testrun with my libstdc-as-dll patch is showing even more fails on top of these, but didn't fail before they appeared, and a quick investigation shows that the executables generated during the testsuite fail to import anything from the libstdc DLL! This could be either a target or a C++ problem since they both co-operate to manage the dllexport attribute. I couldn't find any changes in that area of the backend in the relevant date range, so I've marked it C++ for now. I'll attach preprocessed source for the testcase shortly. -- Summary: dllexport broken on cygwin Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: critical Priority: P3 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: davek at gcc dot gnu dot org GCC build triplet: i686-pc-cygwin GCC host triplet: i686-pc-cygwin GCC target triplet: i686-pc-cygwin http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41512
