This removes the delayed typo correction functionality from Clang (regular typo correction still remains) due to fragility of the solution. An RFC was posted here: https://discourse.llvm.org/t/rfc-removing-support-for-delayed-typo-correction/86631 and while that RFC was asking for folks to consider stepping up to be maintainers, and we did have a few new contributors show some interest, experiments show that it's likely worth it to remove this functionality entirely and focus efforts on improving regular typo correction. This removal fixes ~20 open issues (quite possibly more), improves compile time performance by roughly .3-.4% (https://llvm-compile-time-tracker.com/?config=Overview&stat=instructions%3Au&remote=AaronBallman&sortBy=date), and does not appear to regress diagnostic behavior in a way we wouldn't find acceptable. Fixes #142457 Fixes #139913 Fixes #138850 Fixes #137867 Fixes #137860 Fixes #107840 Fixes #93308 Fixes #69470 Fixes #59391 Fixes #58172 Fixes #46215 Fixes #45915 Fixes #45891 Fixes #44490 Fixes #36703 Fixes #32903 Fixes #23312 Fixes #69874
19 lines
792 B
C
19 lines
792 B
C
// RUN: %clang_cc1 -fsyntax-only -fblocks -ffixed-point -verify %s
|
|
|
|
void GH137860_test(void) {
|
|
struct S {
|
|
char h;
|
|
};
|
|
_Atomic struct S s = { .h = UINT8_MIN }; // expected-error {{use of undeclared identifier 'UINT8_MIN'}}
|
|
__c11_atomic_fetch_add(&s.h, UINT8_MIN); // expected-error {{use of undeclared identifier 'UINT8_MIN'}} \
|
|
expected-error {{accessing a member of an atomic structure or union is undefined behavior}}
|
|
}
|
|
|
|
int (^GH69470) (int i, int j) = ^(int i, int j)
|
|
{ return i / j; }/ j; // expected-error {{use of undeclared identifier 'j'}}
|
|
|
|
void GH69874(void) {
|
|
*a = (a_struct){0}; // expected-error {{use of undeclared identifier 'a'}} \
|
|
expected-error {{use of undeclared identifier 'a_struct'}}
|
|
}
|