Both are implementation-specific (and need not even be identical on a single platform. Early C++ compilers on Windows were incompatible with each other, for example)
But giving the way the Swift compiler is itself written in C++ and tied to the LLVM, i bet it will be "easy" for the Swift compiler team to create interoperability between C++ and Swift.
I think their current goal with ABI compability is one step in that direction.. so it will be just a question of Swift understanding C++ mangling in elf/coff/mach-o objects for the link time, and interpret C++ headers using Clang for the compile time.
Given all that, is not hard to predict that Swift will probably have the best interop with C++ code than any other language out there.
Then there's a second part where i comment about the ability to parse C++ header using Clang when parsing Swift code, so you can get this in compile time. (You probably noted this part and lost some of the information that i've implied from the first).
So, i didnt imply that it was because the Swift compiler was written in C++ that it would have these properties, but because of its history of being tied together with LLVM and Clang, being coded by the same people behind LLVM and Clang.
I hope it gets more clear what i've meant to imply with my comment now.