[llvm-commits] [llvm-gcc-4.2] r110043 - /llvm-gcc-4.2/trunk/gcc/objc/objc-act.c

[Dale Johannesen]

>>>
>>> Hrm.  Well, I guess I could make the test break itself when  
>>> compiled with clang.  You're suggesting
>>>
>>> #if __clang__
>>>         BOGUS XLERB HERE;
>>> #endif
>>>
>>> ?
>>>
>>> However, it wont' be the same diagnostic as llvm-gcc, so I can't  
>>> have the test check for the (llvm-gcc only) diagnostic I want.

#if __clang__
#error text close enough to gcc's error message to fool grep
#endif

It's a real hack, though.  IMO improving the mechanism is a better way  
forward.  Different compilers won't report the same error the same  
way, and the mechanism should understand that.