| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
❌ Integration test FAILEDRequested by @dconeybe on commit fd054fa
Add flaky tests to go/fpl-cpp-flake-tracker |
Sorry, something went wrong.
🍞 Dismissed stale approval on external PR.
| Back | FazBrowse Home | New Git URL |
This is a follow-up to #885 and fixes the Snappy build on some older compilers (e.g. gcc-9.4.0 on linux).
This PR is based on this patch: google/snappy#128
The build error looks like this:
snappy.cc:1017:8: warning: always_inline function might not be inlinable [-Wattributes] 1017 | size_t AdvanceToNextTag(const uint8_t** ip_p, size_t* tag) { | ^~~~~~~~~~~~~~~~ snappy.cc: In function ‘std::pair<const unsigned char*, long int> snappy::DecompressBranchless(const uint8_t*, const uint8_t*, ptrdiff_t, T, ptrdiff_t) [with T = char*]’: snappy.cc:1017:8: error: inlining failed in call to always_inline ‘size_t snappy::AdvanceToNextTag(const uint8_t**, size_t*)’: function body can be overwritten at link time snappy.cc:1097:43: note: called from here 1097 | size_t tag_type = AdvanceToNextTag(&ip, &tag); | ~~~~~~~~~~~~~~~~^~~~~~~~~~~The fix is to explicitly mark AdvanceToNextTag() as inline.
e.g. https://github.com/firebase/firebase-unity-sdk/runs/5998971917