--- Comment #4 from davek at gcc dot gnu dot org 2009-10-03 13:41 ---
(In reply to comment #0)
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
--- Comment #5 from dannysmith at users dot sourceforge dot net 2009-10-03
21:47 ---
(In reply to comment #0)
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:
--
dannysmith at users dot sourceforge dot net changed:
What|Removed |Added
CC||dannysmith at users dot
|
--- Comment #6 from rguenth at gcc dot gnu dot org 2009-10-03 21:54 ---
Yes, it's intended. The fix is as you suggest.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41512
--- Comment #7 from davek at gcc dot gnu dot org 2009-10-03 21:55 ---
(In reply to comment #5)
The breakage can be fixed in target backend i386/winnt-cxx.c
i386_pe_adjust_class_at_definition, by propagating the dllexport attribute
there, rather than relying on DECL_CONTEXT later.
--- Comment #3 from davek at gcc dot gnu dot org 2009-09-30 03:40 ---
Switching to c++ as I suggested initially, there were changes to the handling
of vague linkage and global declarations within the same period, and as I
mentioned nothing that seemed relevant in the backend.
--
