When building a shared libc++.dll, it pulls in libc++abi.a statically with the --wholearchive flag. If such a build is done with --export-all-symbols, I think it's reasonable to assume that everything from that library also should be exported with the same rules as normal local object files, even though we normally avoid autoexporting things from libc++abi.a in other cases when linking a DLL (user code).
Alternatively, as most setups with a static C++ lib would have included all of libc++abi.a in libc++.a, and end user code would never link against libc++abi.a, we could also just remove libc++abi.a from the exclude list?