…yz#3)

…a-xyz#4)

* [BPF] Make rust allocation builtins unavailable for BPF target

- the calls to rust alloc/dealloc routines need to be preserved and
not replaced by compiler generated builtin inlined code

* [SOL][BPF] Adjust BPF tests

* [SOL][BPF] Improve reporting of stack size is too large

- issue only one warning for each function
- report the function location if debug information is available

Co-authored-by: Jack May <[email protected]>

* [SOL] Make lld thread-safe with llvm when used in-process

Every time Solang tries to link a web-assembly file in-process, the linker
re-inits llvm which is not thread-safe with the rest of solang.

Signed-off-by: Sean Young <[email protected]>

* [SOL][BPF] Enable the _ExtInt extension on the BPF Target for Solana

Signed-off-by: Sean Young <[email protected]>

Solana extends BPF so that structs type information is not fully
supported in BTF.  This leads to ICE crashes and some unsupported
relocations being emitted in binary files that linker errors on.
For, now the debug information is simply disabled when compiling
for Solana to avoid the errors in Debug builds.

…stants

RBPF doesn't support R_BPF_64_ABS64 and R_BPF_64_64 correctly
represents relocation information for global data objects, so we can
use them without breaking the correctness of generated object files.

Lower atomic operations to their regular non-atomic equivalents. Lowering for
all operations except atomic fence is done at DAG legalization time. Fences are
removed at instruction emission time.

The actual parameters to a function call are passed in registers for
the first 4 arguments, and on stack for the remaining arguments. The
register $r5 is set to the value of the frame pointer where the actual
parameters are stored. The instruction that copies the frame pointer
into the register $r5 must be glued to the chain of instructions that
sets the previous four call arguments. Otherwise, the scheduler is
free to move the instruction across boundaries of basic blocks and
it's potentially possible that the copy instruction is considered dead
code, even though there's an implicit liveness associated with the
call instruction.

Introduce dynamic stack frames, which are currently opt-in and enabled setting cpu=sbfv2.
When sbfv2 is used, ELF files are flagged with e_flags=EF_SBF_V2 so the runtime can detect it
and react accordingly.

Co-authored-by: Dmitri Makarov <[email protected]>

Adds BPF_SDIV, which is enabled only for the SBF subtarget.

7b107c accidentally reverted it back to an hard error.

…relocations to lld

Co-Authored-By: Richard Patel <[email protected]>

[SOL] emit R_BPF_64_{ABS64, ABS32} for .debug_* sections

Emit e_flags based on the input object files. Ensure that all input files have
the same e_flags as different values signal different ABIs.

Relocate FK_Data_8 fixups as R_BPF_64_ABS64. R_BPF_64_64 is used for ldimm64
which only makes sense in .text.

Currently 64 bit values in non-text sections get chopped to 32 bits and shifted
32 bits to the left (that is, the first 8 bytes of a ldimm64 relocation). This
commit fixes it so that 64 bit values get written fully at the intended offset.

For backwards compatibility, the new behaviour is used only if the reloc-abs64
feature is on (required by -mcpu=sbfv2), since rbpf before
solana-labs/rbpf#301 assumes the legacy buggy layout.

ABS64 relocs were properly implemented in fb7188b

This is a marker feature enabled by default by sbfv2. Enables higher layers to
change syscall impl depending on whether the feature is set or not.

This adds a wrapper around the LLDB executable that resides in the same directory. Once we start to distribute LLDB in sbf-tools, the wrapper + scripts can be put into the same directory as the LLDB executable. Invoking ./solana-lldb will pre-load helper functions to print rust as well as solana types (e.g. pubkeys in base58 or auto deref of accounts) and then start the LLDB executable.

- New SBF back-end subdirectory and corresponding test directories.
- Corresponding changes in ADT, Support, MC, Object, BinaryFormat for
  new SBF architecture and EM_SBF ELF object.
- Corresponding changes in clang to instantiate SBF for Triple::sbf
  rather than the old BPF back-end, etc.
- Corresponding changes in lld to add SBF arch recognition, etc.
- Corresponding changes in llvm-readelf to and opt.

…e syntax. (anza-xyz#54)

- Update the syntax of every instruction in SBFInstrInfo.td (currently
  using the asm variants feature to temporarily support both).
- Update AsmParser for the new syntax (add new operand, memory,
  instruction, and directive parse routines).
- Add error checking for unresolved 16-bit branch relocations and
  emit error message for graceful exit (the old BPF back-end crashes)
  and corresponding lit unit test.
- Add new lit unit tests in MC/SBF and MC/Disassembler/SBF to cover
  disassembly, object emission, and parsing of every single instruction.
  This is more extensive coverage than existed previously.
- Remaster all CodeGen/SBF unit tests accordingly.
- A minor TableGen patch was needed to support asm strings containing
  '|' within variant strings ('|' happens to be the variant separator).

The patch is a bit more complex than it otherwise might be in that we
currently support both syntaxes to ease the verification (e.g., being
able to see and compare each instruction and object code side-by-side
within each unit test). After some 'soak time' for the new functionality,
I intend to remove the old syntax altogether and otherwise clean-up. We'll
also remove the TableGen patch at that time.

Signed-off-by: Lucas Steuernagel <[email protected]>

BTF/CO-RE has been disabled for Solana since:
anza-xyz#37

This patch updates related code (and all applicable unit tests) from roughly
a year of bitrot. This is in preparation for its possible use in the Move
project.

Additionally, a few other 14.0.2022-03-02 -> 15.0-2022-08-09 BPF patches
were reflected in the SBF back-end (e.g., bugfixes).

EM_SBF files are only accepted by new ELF parser of the RBPF.

Because of a bug in BPF backend ABS64 relocations are incorrectly
generated as 64_64 relocations in BPF object files. This temporary
works around this for relocations in .debug section to generate debug
information addresses correctly.

This change rust-lang@ab4fc87
breaks compilation of compiler-rt library for BPF and SBF targets.
For now disabling it.