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

bloom_test: compilation failures with GCC #136

Closed
isaac-io opened this issue Aug 24, 2022 · 0 comments · Fixed by #137
Closed

bloom_test: compilation failures with GCC #136

isaac-io opened this issue Aug 24, 2022 · 0 comments · Fixed by #137
Assignees
Labels
build Build related Upstreamable can be upstreamed to RocksDB
Milestone

Comments

@isaac-io
Copy link
Contributor

Compiling bloom_test with GCC 12 results in the following error:

util/bloom_test.cc: In constructor ‘rocksdb::RawFilterTester::RawFilterTester()’:
util/bloom_test.cc:1012:40: error: member ‘rocksdb::RawFilterTester::data_’ is used uninitialized [-Werror=uninitialized]
 1012 |   RawFilterTester() : metadata_ptr_(&*(data_.end() - 5)) {}
      |                                        ^~~~~

To Reproduce

Run make bloom_test

Expected behavior

Compilation succeeds.

Additional context

N/A

@isaac-io isaac-io added Upstreamable can be upstreamed to RocksDB build Build related labels Aug 24, 2022
@isaac-io isaac-io self-assigned this Aug 24, 2022
isaac-io added a commit that referenced this issue Aug 24, 2022
When compiling bloom_test with GCC 12 it complains about using uninitialised
variables. The error is technically wrong, since only the address is taken,
but since this is a test and there's no performance penalty, initialise
the member to get rid of the error.
@isaac-io isaac-io linked a pull request Aug 24, 2022 that will close this issue
isaac-io added a commit that referenced this issue Aug 24, 2022
When compiling bloom_test with GCC 12 it complains about using uninitialised
variables. The error is technically wrong, since only the address is taken,
but since this is a test and there's no performance penalty, initialise
the member to get rid of the error.
@isaac-io isaac-io added this to the v2.1.0 milestone Sep 21, 2022
isaac-io added a commit that referenced this issue Oct 19, 2022
When compiling bloom_test with GCC 12 it complains about using uninitialised
variables. The error is technically wrong, since only the address is taken,
but since this is a test and there's no performance penalty, initialise
the member to get rid of the error.
isaac-io added a commit that referenced this issue Oct 19, 2022
When compiling bloom_test with GCC 12 it complains about using uninitialised
variables. The error is technically wrong, since only the address is taken,
but since this is a test and there's no performance penalty, initialise
the member to get rid of the error.
isaac-io added a commit that referenced this issue Oct 19, 2022
When compiling bloom_test with GCC 12 it complains about using uninitialised
variables. The error is technically wrong, since only the address is taken,
but since this is a test and there's no performance penalty, initialise
the member to get rid of the error.
isaac-io added a commit that referenced this issue Oct 19, 2022
When compiling bloom_test with GCC 12 it complains about using uninitialised
variables. The error is technically wrong, since only the address is taken,
but since this is a test and there's no performance penalty, initialise
the member to get rid of the error.
isaac-io added a commit that referenced this issue Oct 19, 2022
When compiling bloom_test with GCC 12 it complains about using uninitialised
variables. The error is technically wrong, since only the address is taken,
but since this is a test and there's no performance penalty, initialise
the member to get rid of the error.
Yuval-Ariel pushed a commit that referenced this issue Nov 23, 2022
When compiling bloom_test with GCC 12 it complains about using uninitialised
variables. The error is technically wrong, since only the address is taken,
but since this is a test and there's no performance penalty, initialise
the member to get rid of the error.
Yuval-Ariel pushed a commit that referenced this issue Nov 25, 2022
When compiling bloom_test with GCC 12 it complains about using uninitialised
variables. The error is technically wrong, since only the address is taken,
but since this is a test and there's no performance penalty, initialise
the member to get rid of the error.
Yuval-Ariel pushed a commit that referenced this issue Apr 30, 2023
When compiling bloom_test with GCC 12 it complains about using uninitialised
variables. The error is technically wrong, since only the address is taken,
but since this is a test and there's no performance penalty, initialise
the member to get rid of the error.
udi-speedb pushed a commit that referenced this issue Oct 31, 2023
When compiling bloom_test with GCC 12 it complains about using uninitialised
variables. The error is technically wrong, since only the address is taken,
but since this is a test and there's no performance penalty, initialise
the member to get rid of the error.
udi-speedb pushed a commit that referenced this issue Dec 3, 2023
When compiling bloom_test with GCC 12 it complains about using uninitialised
variables. The error is technically wrong, since only the address is taken,
but since this is a test and there's no performance penalty, initialise
the member to get rid of the error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Build related Upstreamable can be upstreamed to RocksDB
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant