possible gcc bug?

[Skunk Worx]

Hi,

I have an EPEL 6, 64 bit system (SL6) and an fc17 64 bit system.

My shared library uses boost, code synthesis xsd cxx-tree, and xerces-c.

There may be a bug in gcc that prevents this shared library from being 
dlclose()'ed properly :

http://gcc.gnu.org/ml/gcc-help/2011-05/msg00403.html

fc17:

host: Loading libchild.so...
child: Constructor
host: so = 0xc0a030
host: Unloading libchild.so...
host: Unloaded.
host: (nil)
child: Destructor

The following sub-thread implies that this started affecting some 
distributions around gcc version 4.6.0 :

http://gcc.gnu.org/ml/gcc-help/2011-05/msg00432.html

However my EPEL 6 64 is gcc / Red Hat 4.4.6-3 and exhibits the same 
behavior.

Do you think this is a "won't fix" or "not a bug"?

Regards,
John