This test dates from the time when llvm-gcc had problems if two types were

This test dates from the time when llvm-gcc had problems if two types were
named the same, so it had to qualify type names according to the enclosing
scope to ensure uniqueness.  This is no longer needed for correctness (though
it may be helpful when reading the IR), so this test has lost its importance.
Zap it because dragonegg will never be able to produce the qualified type name
since modern gcc zaps language specific info (such as whether a type is nested
inside another - needed to get X::Y here) before dragonegg is reached.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@120721 91177308-0d34-0410-b5e6-96231b3b80d8