[llvm] [BPF] Define empty set of BPF libcalls (PR #169537)

[Alessandro Decina via llvm-commits]

alessandrod wrote:

I fail to see what this PR is fixing: what gets better? What use case gets unlocked? As things are now, this is just an unnecessary breaking change for the whole rust eBPF ecosystem.

>     3. Create a separate ABI and triple to handle cases that may need libcalls to work with the BPF target.

Sure by all means go ahead and do that. Once you have the new triple working, supported in rustc, and a migration path for rust eBPF program, I have nothing against removing libcall support from the current triple. 


https://github.com/llvm/llvm-project/pull/169537