
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
21 lines
1.2 KiB
C
21 lines
1.2 KiB
C
// RUN: %clang_cc1 %s -fsyntax-only -verify -pedantic
|
|
void check(int);
|
|
void a(void) {
|
|
check(__builtin_isfinite(1.0f));
|
|
check(__builtin_isinf(1.0));
|
|
check(__builtin_isinf_sign(1.0L));
|
|
check(__builtin_isnan(1.0f));
|
|
check(__builtin_isnormal(1.0f));
|
|
check(__builtin_isfinite(1)); // expected-error{{requires argument of floating point type}}
|
|
check(__builtin_isinf()); // expected-error{{too few arguments}}
|
|
check(__builtin_isnan(1,2)); // expected-error{{too many arguments}}
|
|
check(__builtin_fpclassify(0, 0, 0, 0, 0, 1.0));
|
|
check(__builtin_fpclassify(0, 0, 0, 0, 0, 1)); // expected-error{{requires argument of floating point type}}
|
|
check(__builtin_fpclassify(0, 1, 2, 3, 4.5, 5.0)); // expected-warning{{implicit conversion from 'double' to 'int' changes value from 4.5 to 4}}
|
|
check(__builtin_fpclassify(0, 0, 0, 0, 1)); // expected-error{{too few arguments}}
|
|
check(__builtin_fpclassify(0, 0, 0, 0, 0, 1, 0)); // expected-error{{too many arguments}}
|
|
|
|
check(__builtin_fpclassify(0,0,0,0,0, (invalid))); // expected-error{{use of undeclared identifier 'invalid'}}
|
|
check(__builtin_fpclassify(0,0,0,0,0, (inf))); // expected-error{{use of undeclared identifier 'inf'}}
|
|
}
|