xz maintainer just pushed this "CMake: Fix sabotaged Landlock sandbox check." commit
https://git.tukaani.org/?p=xz.git;a=commitdiff;h=f9cf4c05edd...
That said, does GCC accept every non-printing character as whitespace? If not, they could probably have achieved the same thing with a narrow-nonbreaking-space character or similar.
~/t [main L|…1]$ gcc test.c
~/t [main L|…1]$ vi test.c
~/t [main L| 1…1]$ git diff
diff --git a/test.c b/test.c
index 33c14ce..dc93007 100644
--- a/test.c
+++ b/test.c
@@ -1,3 +1,3 @@
int main() {
- return 0;
+ return 0;
}
~/t [main L| 1…1]$ gcc test.c
test.c:2:5: error: expected expression
<U+0008>return 0;
^
1 error generated.
So, yes, this could have been made to look exactly like a meaningless whitespace change.