[all-commits] [llvm/llvm-project] 14d4d0: RuntimeLibcalls: Really move default libcall handl...
Matt Arsenault via All-commits
all-commits at lists.llvm.org
Mon Jul 14 22:23:13 PDT 2025
Branch: refs/heads/users/arsenm/runtime-libcalls/use-tablegen-default-handling
Home: https://github.com/llvm/llvm-project
Commit: 14d4d03472d94e8d2a017d03ca2399a276e2f44f
https://github.com/llvm/llvm-project/commit/14d4d03472d94e8d2a017d03ca2399a276e2f44f
Author: Matt Arsenault <Matthew.Arsenault at amd.com>
Date: 2025-07-15 (Tue, 15 Jul 2025)
Changed paths:
M llvm/include/llvm/IR/RuntimeLibcalls.h
M llvm/include/llvm/IR/RuntimeLibcalls.td
M llvm/lib/IR/RuntimeLibcalls.cpp
M llvm/test/TableGen/RuntimeLibcallEmitter.td
M llvm/utils/TableGen/Basic/RuntimeLibcallsEmitter.cpp
Log Message:
-----------
RuntimeLibcalls: Really move default libcall handling to tablegen
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.
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list