if (getLangOptions().Microsoft) return New;
- // Redeclaration of a type is a constraint violation (6.7.2.3p1).
+ // C++ [dcl.typedef]p2:
+ // In a given non-class scope, a typedef specifier can be used to
+ // redefine the name of any type declared in that scope to refer
+ // to the type to which it already refers.
+ if (getLangOptions().CPlusPlus && !isa<CXXRecordDecl>(CurContext))
+ return New;
+
+ // In C, redeclaration of a type is a constraint violation (6.7.2.3p1).
// Apparently GCC, Intel, and Sun all silently ignore the redeclaration if
// *either* declaration is in a system header. The code below implements
// this adhoc compatibility rule. FIXME: The following code will not
--- /dev/null
+// RUN: clang -fsyntax-only -verify %s
+
+typedef int INT;
+typedef INT REALLY_INT; // expected-error{{previous definition is here}}
+typedef REALLY_INT REALLY_REALLY_INT;
+typedef REALLY_INT BOB;
+typedef float REALLY_INT; // expected-error{{typedef redefinition with different types ('float' vs 'INT')}}
+
+class X {
+ typedef int result_type; // expected-error{{previous definition is here}}
+ typedef INT result_type; // expected-error{{redefinition of 'result_type'}}
+};