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

release-19.2: build: always specify PORTABLE=1 when building RocksDB #59018

Conversation

petermattis
Copy link
Collaborator

Something recently changed on the TC agents (presumably usage of a new
machine type with a different CPU) so that using -march=native when
building RocksDB causes AVX512 instructions to be used which are not
present on roachprod machines. The result is that binaries built in this
way will die with "illegal instruction". RocksDB has a mechanism to
disable the use of -march=native: pass PORTABLE=1 to the make
command. We were already doing this for release builds. Now we're doing
it for all builds.

Fixes #58754

Release note: none

@cockroach-teamcity
Copy link
Member

This change is Reviewable

Something recently changed on the TC agents (presumably usage of a new
machine type with a different CPU) so that using `-march=native` when
building RocksDB causes AVX512 instructions to be used which are not
present on roachprod machines. The result is that binaries built in this
way will die with "illegal instruction". RocksDB has a mechanism to
disable the use of `-march=native`: pass `PORTABLE=1` to the make
command. We were already doing this for release builds. Now we're doing
it for all builds.

Fixes cockroachdb#58754

Release note: none
@petermattis petermattis force-pushed the pmattis/rocksdb-portable-19.2 branch from 608abc6 to 61a8890 Compare January 15, 2021 01:32
@petermattis
Copy link
Collaborator Author

TFTR!

@petermattis petermattis merged commit e9e3265 into cockroachdb:release-19.2 Jan 15, 2021
@petermattis petermattis deleted the pmattis/rocksdb-portable-19.2 branch January 15, 2021 01:57
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