aboutsummaryrefslogtreecommitdiff
path: root/clang/test/SemaCXX/warn-unsafe-buffer-usage-libc-functions-inline-namespace.cpp
diff options
context:
space:
mode:
authorMatt Arsenault <Matthew.Arsenault@amd.com>2025-08-04 08:32:00 +0900
committerGitHub <noreply@github.com>2025-08-04 08:32:00 +0900
commitb2f0ffd659e7eb3d17fedad5de21a122cc58c4ef (patch)
treeb989cd86f3e37207ddc1026ddb18ccb9ef7acb6b /clang/test/SemaCXX/warn-unsafe-buffer-usage-libc-functions-inline-namespace.cpp
parent7efb70ff6f4d061652970fdbef208cfbcaf02198 (diff)
downloadllvm-b2f0ffd659e7eb3d17fedad5de21a122cc58c4ef.zip
llvm-b2f0ffd659e7eb3d17fedad5de21a122cc58c4ef.tar.gz
llvm-b2f0ffd659e7eb3d17fedad5de21a122cc58c4ef.tar.bz2
RuntimeLibcalls: Really move default libcall handling to tablegen (#148780)
Hack in the default setting so it's consistently generated like the other cases. Maintain a list of targets where this applies. The alternative would require new infrastructure to sort the system library initialization in some way. I wanted the unhandled target case to be treated as a fatal error, but it turns out there's a hack in IRSymtab using RuntimeLibcalls, which will fail out in many tests that do not have a triple set. Many of the failures are simply running llvm-as with no triple, which probably should not depend on knowing an accurate set of calls.
Diffstat (limited to 'clang/test/SemaCXX/warn-unsafe-buffer-usage-libc-functions-inline-namespace.cpp')
0 files changed, 0 insertions, 0 deletions