Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update Rust to 1.75.0 #88

Merged
merged 100 commits into from
Feb 20, 2024
Merged

Update Rust to 1.75.0 #88

merged 100 commits into from
Feb 20, 2024

Conversation

LucasSte
Copy link
Collaborator

No description provided.

jackcmay and others added 30 commits February 19, 2024 15:37
@jackcmay @LucasSte
[SOL] Use Solana's LLVM fork
fd2bb85
@jackcmay @LucasSte
[SOL] Enable LLVM backend
ff860ee
@jackcmay @LucasSte
[SOL] Implement C abi modifier
2a9c2f2
@jackcmay @LucasSte
[SOL] Add custom build configuration
5055958
@jackcmay @LucasSte
[SOL] Don't build rustdoc to save time
aeba635
@jackcmay @LucasSte
[SOL] Custom README.md
d6c5784
@jackcmay @LucasSte
[SOL] Add build script
048e84c
@jackcmay @LucasSte
[SOL] Preserve lib dir, needed for sysroot building
9eac64d
@jackcmay @LucasSte
[SOL] Allow older gcc, debian does not support a newer one yet
5a2fbc2
@jackcmay @LucasSte
[SOL] Reduce size of output binaries
d84abc8
@jackcmay @LucasSte
[SOL] Add BPF as a built-in target
3bcbaf3
@jackcmay @LucasSte
[SOL] Add bin dir later
abf8c7b
@jackcmay @LucasSte
[SOL] Update README.md
936906f
@jackcmay @LucasSte
[SOL] Script nit
61fce1f
@jackcmay @LucasSte
[SOL] BPF Spec use os=unknown
b8c731d
@jackcmay @LucasSte
[SOL] Rust libstd requires atomic cas support
3a19b1c
@jackcmay @LucasSte
[SOL] Updates from latest config.example.toml
6bb03a0
@jackcmay @LucasSte
[SOL] Updates from rust 1.39
f342fe9
@jackcmay @LucasSte
[SOL] Allow all nightly options to help interactions with newer Cargo
875ed2b
@veryoddthomas @LucasSte
[SOL] Update README.md
ca68c1c 
Fix typo
@Lichtso @LucasSte
[SOL] Renames to match the upstream changes
b04b686 
- d4d1111 "The target configuration option `abi_blacklist` has been renamed to `unsupported_abis`."
- 6567154 "rustc_target: rename {Fn,Arg}Type to {Fn,Arg}Abi."
@dmakarov @LucasSte
[SOL] Disable eh_frame_hdr linker option
8d2104c
@jackcmay @LucasSte
[SOL] Build llvm tools from llvm-project
967de63
@jackcmay @LucasSte
[SOL] Link llvm tools statically
d75161f
@dmakarov @LucasSte
[SOL] Do not disable all builtins for BPF target
e28e9c0
@dmakarov @LucasSte
[SOL] Adjust ABI implementation to pass 128-bit arguments by value
2d55891
@dmakarov @LucasSte
[SOL] Adjust BPF target spec to upstream changes
621bfcc
@dmakarov @LucasSte
[SOL] Adjust for building in tree the bpf target with std library
5a8a2c7
@dmakarov @LucasSte
[SOL] Update build script to automatically build for correct targets
23da387
@dmakarov @LucasSte
[SOL] Use +solana feature when compiling for BPF target
a12b51e
alessandrod and others added 25 commits February 19, 2024 15:37
@alessandrod @LucasSte
[SOL] sbf: implement static-syscalls target feature
678b663 
Expose static-syscalls as a rust target-feature so it can be used with
conditional compilation and implement sol_log_(), abort() and sol_alloc_free_()
as static syscalls.

This bumps src/llvm-project to pull the corresponding LLVM change.
@alessandrod @LucasSte
[SOL] sbfv2: place the rodata segment at MM_PROGRAM_START
aaf3ec0 
With this _RELATIVE relocations can be ignored in the vm. Relocations are still
produced in case we change address space layout in the future.
@alessandrod @LucasSte
[SOL] sbfv2: output _RELATIVE relocations in a separate SHT_RELR section
4fdc87d 
sbfv2 only produces _RELATIVE relocations and those can be packed much more
efficiently using SHT_RELR. See https://reviews.llvm.org/D48247.
@alessandrod @LucasSte
[SOL] tests: update docker image name
306ae1e
@dmakarov @LucasSte
[SOL] Update run-bpf-tests revision in CI
606c944
@dmakarov @LucasSte
[SOL] Update run-bpf-tests revision in CI
a44a1c9
@dmakarov @LucasSte
[SOL] Adjust BPF customization after upgrading to rust 1.62.0
71b23af
@dmakarov @LucasSte
[SOL] Update cargo-run-bpf-test revision for CI
5d82320
@dmakarov @LucasSte
[SOL] Update run-sbf-tests revision in CI
235f439
@dmakarov @LucasSte
[SOL] switch to new SBF LLVM backend
869ffd7
@dmakarov @LucasSte
[SOL] Adjust SBF customization after upgrading to rust 1.65.0
61817e6
@dmakarov @LucasSte
[SOL] Update run-sbf-tests revision in CI
a579ea6
@dmakarov @LucasSte
[SOL] Temporarily patch BPF ELF file header with SBF machine code
0a37947
@dmakarov @LucasSte
[SOL] Update run-sbf-tests revision in CI
47f08f7
@dmakarov @LucasSte
[SOL] Add lldb to enabled projects in [llvm] section of config.toml
876947c
@dmakarov @LucasSte
[SOL] Fix Ci error caused by insufficient git history fetched
672d7bc
@dmakarov @LucasSte
[SOL] Temporarily patch BPF ELF file header only for SBFv2 cpu
ff57430
@dmakarov @LucasSte
[SOL] Update run-sbf-tests revision in CI
900683a
@dmakarov @LucasSte
[SOL] Adjust SBF customization after upgrading to rust 1.68.0
cb8ed9c
@dmakarov @LucasSte
[SOL] Set default visibility of symbols in SBF binaries to hidden
4383239 
Make a solana specific version of __rdl_oom handler that doesn't use a
static variable.  This variable can't be supported is Solana execution
environment.
@dmakarov @LucasSte
[SOL] Update run-sbf-tests revision in CI
96993e4
@dmakarov @LucasSte
[SOL] Adjust SBF customization after upgrading to rust 1.72.0
0da9b0a
@dmakarov @LucasSte
[SOL] Fix CI failures
224302f
@LucasSte
[SOL] Adjust compiler after upgrade to 1.75.0
bf80789
@LucasSte
[SOL] Adjust flaky CI test
bcaa393
@LucasSte
Copy link
Collaborator Author

I used this hack for freeing up space in the CI runner:

actions/runner-images#2840 (comment)

@LucasSte LucasSte merged commit 922e7b9 into anza-xyz:solana-1.75.0 Feb 20, 2024
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dmakarov dmakarov dmakarov approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
10 participants
@LucasSte @dmakarov @jackcmay @veryoddthomas @Lichtso @joncinque @alessandrod @lithdew @brson @Aimeedeer