en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/VFS/module_missing_vfs.m#7d644e12 [C11/C2x] Change the behavior of the implicit function declaration warningC89 had a questionable feature where the compiler would implicitlydeclare a function that the user called but was never previouslydeclared. The resulting function would be globally declared asextern int func(); -- a function without a prototype which accepts zeroor more arguments.C99 removed support for this questionable feature due to severesecurity concerns. However, there was no deprecation period; C89 hadthe feature, C99 didn't. So Clang (and GCC) both supported thefunctionality as an extension in C99 and later modes.C2x no longer supports that function signature as it now requires allfunctions to have a prototype, and given the known security issues withthe feature, continuing to support it as an extension is not tenable.This patch changes the diagnostic behavior for the-Wimplicit-function-declaration warning group depending on the languagemode in effect. We continue to warn by default in C89 mode (due to thefeature being dangerous to use). However, because this feature will notbe supported in C2x mode, we've diagnosed it as being invalid for solong, the security concerns with the feature, and the trivialworkaround for users (declare the function), we now default theextension warning to an error in C99-C17 mode. This still gives usersan easy workaround if they are extensively using the extension in thosemodes (they can disable the warning or use -Wno-error to downgrade theerror), but the new diagnostic makes it more clear that this feature isnot supported and should be avoided. In C2x mode, we no longer allow animplicit function to be defined and treat the situation the same as anyother lookup failure.Differential Revision: https://reviews.llvm.org/D122983 List of files: /llvm-project-15.0.7/clang/test/VFS/module_missing_vfs.m Wed, 20 Apr 2022 15:25:35 +0000 Aaron Ballman <aaron@aaronballman.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/VFS/module_missing_vfs.m#32789485 Fix `sed -e s@FOO@%/S@` and similar when there's @'s in the working directoryJenkins sometimes starts a new working directory by appending @2 (orincrementing the number if the @n suffix is already there). This causesseveral clang tests to fail as: s@INPUT_DIR@%/S/Inputs@ggets expanded to the invalid: s@INPUT_DIR@/path/to/workdir@2/Inputs@g ~~~~~~~~~~where the part marked with ~'s is interpreted as the flags. These areinvalid and the test fails.Previous fixes simply exchanged the @ character for another like | butthat's just moving the problem. Address it by adding an expansion thatescapes the @ character we're using as a delimiter as well as other magiccharacters in the replacement of sed's s@@@.There's still room for expansions to cause trouble though. One I ran intowhile testing this was that having a directory called foo@bar causes lotsof `CHECK-NOT: foo` directives to match. There's also things likedirectories containing `\1` List of files: /llvm-project-15.0.7/clang/test/VFS/module_missing_vfs.m Tue, 03 Dec 2019 23:22:30 +0000 Daniel Sanders <daniel_l_sanders@apple.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/VFS/module_missing_vfs.m#a685f516 Start porting ivfsoverlay tests to WindowsPart of PR43272, the changes are:1. Use @ as the sed pattern delimiter instead of : so that the driveletter in lit substitutions isn't an issue.2. Use the %/t and %/S substitutions to get paths with forward slashesto work around string quoting issues in the yaml file.3. Replace REQUIRES:shell with XFAIL:windows. These tests should pass onWindows, but do not for reasons that are not yet understood. We wouldlike to know if they pass unexpectedly.I was able to remove the XFAILs from two tests, since they already passwith my sed fix: clang/test/VFS/module_missing_vfs.m clang/test/VFS/test_nonmodular.cReviewers: amccarthDifferential Revision: https://reviews.llvm.org/D67454llvm-svn: 371663 List of files: /llvm-project-15.0.7/clang/test/VFS/module_missing_vfs.m Wed, 11 Sep 2019 20:56:25 +0000 Reid Kleckner <rnk@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/VFS/module_missing_vfs.m#005c2e57 [vfs] Don't bail out after a missing -ivfsoverlay fileThis make -ivfsoverlay behave more like other fatal errors (e.g. missing-include file) by skipping the missing file instead of bailing out ofthe whole compilation. This makes it possible for libclang to stillprovide some functionallity as well as to correctly produce the fatalerror diagnostic (previously we lost the diagnostic in libclang sincethere was no TU to tie it to).rdar://33385423llvm-svn: 328337 List of files: /llvm-project-15.0.7/clang/test/VFS/module_missing_vfs.m Fri, 23 Mar 2018 17:37:27 +0000 Ben Langmuir <blangmuir@apple.com>