Ld relocation warning for polymorphic class declared __symbolic

Question

The SDN article [Reducing Symbol Scope with Sun Studio C/C++|http://developers.sun.com/solaris/articles/symbol_scope.html|By Giri Mandalika, May, 2005 (revised March 22, 2006) ] says that:
The mixed use of -xldscope=hidden and __symbolic will yield the same effect as __declspec(dllexport) in DLLs on Windows (explained in the later part of the article).
However, the Solaris 10 linker (version 5.10-1.482) issues a relocation warning for polymorphic classes declared with the __symbolic specifier, a common practice in DLLs on Windows. The same happens when using the new Sun C++ 5.9 specifier __declspec(dllexport) when building the .so and dllimport when using it as discussed later in the referenced SDN article.
Is the comment in the article incorrect or is the linker buggy?
$    cat t.cpp \
  && CC -PIC -DEXPORT=__symbolic -xldscope=hidden -c t.cpp \
  && CC -G -o libt.so t.o \
  && CC -DEXPORT=__global -DMAIN -c t.cpp \
  && CC -o t t.o -L. -lt
struct EXPORT B { virtual ~B (); };
#ifdef MAIN
int main () { B b; }
#else
B::~B () { }
#endif
ld: warning: relocation warning: R_SPARC_COPY: file ./libt.so: symbol B::__vtbl: relocation bound to a symbol with STV_PROTECTED visibility

Answer 1

The __global on the declaration is needed in order for the linker to resolve references to the symbol when using it (i.e., in the executable or another .so). Replacing __global with __symbolic on the declaration prevents the executable from linking. Dropping the __global altogether cause the same warning as with __global.
Btw., the same warning is issued for global data (see below). In the Suggestions on establishing an object interface, the article says:
>
2. Define all interface symbols using the __symbolic directive, data objects using the __global directive and reduce all other symbols to local using the -xldscope=hidden compiler option.
>
which is again different from the Windows approach, just like in the case of polymorphic classes. Since virtual tables are essentially global objects, the warning seems consistent and suggests that the article is wrong in claiming that:
>
The mixed use of -xldscope=hidden and __symbolic will yield the same effect as __declspec(dllexport) in DLLs on Windows...
>
$    cat t.cpp \
  && CC -KPIC -DEXPORT=__symbolic -xldscope=hidden -c +w t.cpp\
  && CC -G -o libt.so t.o \
  && CC -DEXPORT=__global -DMAIN -c t.cpp \
  && CC +w -o t t.o -L. -lt
extern EXPORT int* a;
#ifdef MAIN
int main() { a = 0; }
#else
int *a;
#endif
ld: warning: relocation warning: R_SPARC_COPY: file ./libt.so: symbol a: relocation bound to a symbol with STV_PROTECTED visibility