System Platform Abstraction Layer

Oct 13, 2025 by miodeya.com 37 views

Introduction

In order for the Rust code written for applications and libraries to be compatible with the Solana Runtime Environment, a fork of the Rust Compiler with the required changes has been made by Anza. The compatibility of stable-mir-json with Solana applications and libraries is therefore dependent on its compatibility with the Anza fork. This issue will document the compatibility with the Anza fork, and detail the intended user experience.

The Anza Rust Fork

The Anza Rust fork has several differences compared to the original Rust Compiler. These differences can be summarized as follows:

1. The Anza Rust Fork Itself

The Anza Rust fork tracks different version numbers to the origin Rust, but does not contain minor differences inside the compiler directory. However, there are some differences that can be reduced to the support for a different target added for sbf-solana-solana.

Target Support: The Anza Rust fork includes support for the sbf-solana-solana target, which is not present in the original Rust Compiler.
Version Numbers: The Anza Rust fork tracks different version numbers to the origin Rust, which may affect the compatibility of stable-mir-json with Solana applications and libraries.

2. Standard Library

The standard library of the Anza Rust fork has its system platform abstraction layer extended to support the sbf-solana-solana target. Certain functionality is restricted here, and the functionality that can interact with the Solana Runtime Environment is called with an extern "C" call to a murmur32 hash of the function name.

System Platform Abstraction Layer: The standard library of the Anza Rust fork includes an extended system platform abstraction layer to support the sbf-solana-solana target.
Functionality Restriction: Certain functionality is restricted in the standard library of the Anza Rust fork, and the functionality that can interact with the Solana Runtime Environment is called with an extern "C" call to a murmur32 hash of the function name.

3. Compiler-Builtins

There are some memory functions implemented in the same fashion as the standard library in a fork of the compiler-builtins.

Memory Functions: The Anza Rust fork includes memory functions implemented in the same fashion as the standard library.
Compiler-Builtins: The Anza Rust fork includes a fork of the compiler-builtins, which includes memory functions implemented in the same fashion as the standard library.

Stable MIR JSON Requirements

Stable MIR JSON requires the following:

1. Serialization of Stable MIR

The inclusion of serialization of stable MIR in the compiler is required, which was merged in this PR.

Serialization of Stable MIR: The inclusion of serialization of stable MIR in the compiler is required.
PR: The serialization of stable MIR was merged in this PR.

2. Similarity to Nightly Version

Ideally, for the MIR and Stable MIR access points to be similar to the source of nightly-2024-11-29 (or later).

Similarity to Nightly Version: The MIR and Stable MIR access points should be similar to the source of nightly-2024-11-29 (or later).

Possible Solutions

There are several possible solutions to the compatibility issue with the Anza fork:

1. Modular Replacement of Standard Library and Compiler-Builtins

It might be tempting to think that because most of the differences are in the std lib and compiler builtins for the Anza fork that it would be possible to keep the Stable MIR nightly version we have been working off so far and plug the std lib and builtins in modularly. However, attempting to exchange std lib with compilers is not recommended and is unlikely to succeed - and this would not account for the necessary inclusion of sbf-solana-solana target.

Modular Replacement: Attempting to exchange std lib with compilers is not recommended and is unlikely to succeed.
Necessary Inclusion: The necessary inclusion of sbf-solana-solana target is not accounted for in this solution.

2. Upgrading the Anza Fork to a Recent Version of Rustc

Anza upgrades the fork to a recent version of rustc. Lucas mentioned that he was in the process of upgrading the solana fork to version 1.84.0 of rustc. This is stratifies both 1. and 2. the requirements listed for Stable MIR JSON.

Upgrading the Anza Fork: Anza upgrades the fork to a recent version of rustc.
Recent Version of Rustc: The recent version of rustc is version 1.84.0.
Stratifies Requirements: This solution stratifies both 1. and 2. the requirements listed for Stable MIR JSON.
Frequently Asked Questions (FAQs) about Compatibility with Anza Fork ====================================================================

Q: What is the Anza Rust fork?

A: The Anza Rust fork is a modified version of the Rust Compiler that includes the required changes for compatibility with the Solana Runtime Environment.

Q: What are the differences between the Anza Rust fork and the original Rust Compiler?

A: The Anza Rust fork has several differences compared to the original Rust Compiler, including:

Target Support: The Anza Rust fork includes support for the sbf-solana-solana target, which is not present in the original Rust Compiler.
Version Numbers: The Anza Rust fork tracks different version numbers to the origin Rust, which may affect the compatibility of stable-mir-json with Solana applications and libraries.
Standard Library: The standard library of the Anza Rust fork has its system platform abstraction layer extended to support the sbf-solana-solana target.
Compiler-Builtins: The Anza Rust fork includes memory functions implemented in the same fashion as the standard library in a fork of the compiler-builtins.

Q: What are the requirements for Stable MIR JSON?

A: Stable MIR JSON requires the following:

Serialization of Stable MIR: The inclusion of serialization of stable MIR in the compiler is required.
Similarity to Nightly Version: Ideally, for the MIR and Stable MIR access points to be similar to the source of nightly-2024-11-29 (or later).

Q: What are the possible solutions to the compatibility issue with the Anza fork?

A: There are several possible solutions to the compatibility issue with the Anza fork, including:

Modular Replacement of Standard Library and Compiler-Builtins: Attempting to exchange std lib with compilers is not recommended and is unlikely to succeed.
Upgrading the Anza Fork to a Recent Version of Rustc: Anza upgrades the fork to a recent version of rustc, which stratifies both 1. and 2. the requirements listed for Stable MIR JSON.

Q: What is the current status of the Anza fork upgrade?

A: Lucas mentioned that he was in the process of upgrading the solana fork to version 1.84.0 of rustc.

Q: How will the compatibility issue with the Anza fork be resolved?

A: The compatibility issue with the Anza fork will be resolved by upgrading the Anza fork to a recent version of rustc, which stratifies both 1. and 2. the requirements listed for Stable MIR JSON.

Q: What are the benefits of resolving the compatibility issue with the Anza fork?

A: Resolving the compatibility issue with the Anza fork will enable the use of stable-mir-json with Solana applications and libraries, which will improve the overall performance and reliability of the Solana Runtime Environment.

Q: What are the next steps in resolving the compatibility issue with the Anza fork?

A: The next steps in resolving the compatibility issue with the Anza fork are:

Upgrading the Anza Fork: Upgrade the Anza fork to a recent version of rustc.
Testing and Verification: Test and verify the compatibility of stable-mir-json with Solana applications and libraries.
Deployment: Deploy the upgraded Anza fork and stable-mir-json to the Solana Runtime Environment.