diff options
| author | Sam Clegg <sbc@chromium.org> | 2022-10-03 08:04:58 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-03 08:04:58 -0700 |
| commit | 50b0b6da61c1ac4c2b4f27256a038a70a200c3df (patch) | |
| tree | 2ad47f23e8bfbde65479ad610cf2b469f093da88 | |
| parent | 22f0f3ae45c9dc7d091282974d013ab340754b6e (diff) | |
| download | binaryen-50b0b6da61c1ac4c2b4f27256a038a70a200c3df.tar.gz binaryen-50b0b6da61c1ac4c2b4f27256a038a70a200c3df.tar.bz2 binaryen-50b0b6da61c1ac4c2b4f27256a038a70a200c3df.zip | |
Fix compiler warnings under emcc. NFC (#5104)
These comparisons were showing up as warnings with the latest
emcc/clang. I only noticed because I ran `ninja` to build everything
whereas we only test the `binaryen` target under emscripten normally.
| -rw-r--r-- | test/gtest/type-builder.cpp | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/test/gtest/type-builder.cpp b/test/gtest/type-builder.cpp index bc7b72e5d..94a2a1f80 100644 --- a/test/gtest/type-builder.cpp +++ b/test/gtest/type-builder.cpp @@ -25,12 +25,12 @@ TEST_F(TypeTest, TypeIterator) { EXPECT_EQ(none.size(), 0u); EXPECT_EQ(none.begin(), none.end()); - EXPECT_EQ(none.end() - none.begin(), 0u); + EXPECT_EQ(none.end() - none.begin(), 0); EXPECT_EQ(none.begin() + 0, none.end()); EXPECT_EQ(i32.size(), 1u); EXPECT_NE(i32.begin(), i32.end()); - EXPECT_EQ(i32.end() - i32.begin(), 1u); + EXPECT_EQ(i32.end() - i32.begin(), 1); EXPECT_EQ(*i32.begin(), i32); EXPECT_EQ(i32[0], i32); @@ -56,7 +56,7 @@ TEST_F(TypeTest, TypeIterator) { EXPECT_EQ(tuple.size(), 4u); EXPECT_NE(tuple.begin(), tuple.end()); - EXPECT_EQ(tuple.end() - tuple.begin(), 4u); + EXPECT_EQ(tuple.end() - tuple.begin(), 4); EXPECT_EQ(*tuple.begin(), i32); EXPECT_EQ(*(tuple.begin() + 1), i64); |