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.

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

Do not mandate use of SHA-NI instruction #11973

Merged
merged 1 commit into from
Aug 20, 2024
Merged

Conversation

nagisa
Copy link
Collaborator

@nagisa nagisa commented Aug 20, 2024

That said, development currently happens on machines with this
instruction enabled and our fee structure will assume use of this
instruction in the long run, meaning that this instruction will become
required to keep up with the network in due time anyway.

This also fixes other feature names. I had looked at the LLVM names,
rather than Rust ones in the list 🤦

@nagisa nagisa requested a review from robin-near August 20, 2024 07:39
@nagisa nagisa requested a review from a team as a code owner August 20, 2024 07:39
Copy link

codecov bot commented Aug 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.54%. Comparing base (785d549) to head (1c62ae0).
Report is 4 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #11973      +/-   ##
==========================================
- Coverage   71.59%   71.54%   -0.06%     
==========================================
  Files         808      810       +2     
  Lines      163588   163865     +277     
  Branches   163588   163865     +277     
==========================================
+ Hits       117125   117238     +113     
- Misses      41381    41548     +167     
+ Partials     5082     5079       -3     
Flag Coverage Δ
backward-compatibility 0.23% <ø> (-0.01%) ⬇️
db-migration 0.23% <ø> (-0.01%) ⬇️
genesis-check 1.33% <ø> (-0.01%) ⬇️
integration-tests 38.44% <ø> (-0.03%) ⬇️
linux 71.31% <ø> (-0.05%) ⬇️
linux-nightly 71.11% <ø> (-0.08%) ⬇️
macos 54.37% <ø> (-0.04%) ⬇️
pytests 1.60% <ø> (-0.01%) ⬇️
sanity-checks 1.40% <ø> (-0.01%) ⬇️
unittests 65.63% <ø> (-0.06%) ⬇️
upgradability 0.28% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@nagisa nagisa enabled auto-merge August 20, 2024 08:18
@nagisa nagisa requested a review from bowenwang1996 August 20, 2024 16:54
@nagisa nagisa changed the title fix: unstable and wrong target feature names Do not mandate use of SHA-NI instruction Aug 20, 2024
That said, development currently happens on machines with this
instruction enabled and our fee structure will assume use of this
instruction in the long run, meaning that this instruction will become
required to keep up with the network in due time anyway.

This also fixes other feature names. I had looked at the LLVM names,
rather than Rust ones in the list 🤦
@nagisa nagisa added this pull request to the merge queue Aug 20, 2024
Merged via the queue into near:master with commit 6c39e40 Aug 20, 2024
30 checks passed
@nagisa nagisa deleted the fix-cpu-features branch August 20, 2024 17:35
@haferman
Copy link

Thank you! This gives me time to upgrade my server.

jancionear pushed a commit that referenced this pull request Aug 21, 2024
That said, development currently happens on machines with this
instruction enabled and our fee structure will assume use of this
instruction in the long run, meaning that this instruction will become
required to keep up with the network in due time anyway.

This also fixes other feature names. I had looked at the LLVM names,
rather than Rust ones in the list 🤦
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants