Andrew Kryczka

> edit: Oh, I did miss something. It would only be persisted if compaction hit the incorrect block in block cache. If a user read hit it it would just...

disassembly shows: ``` 180546c29: c4 42 50 f5 c6 bzhi %ebp,%r14d,%r8d ``` `bzhi` is part of BMI2: https://en.wikipedia.org/wiki/X86_Bit_manipulation_instruction_set#BMI2_(Bit_Manipulation_Instruction_Set_2) I also don't know why the compiler outputs BMI2 instructions when portable...

Thank you for the pointer. I have not found anywhere we are compiling Snappy for the Windows build, although we do compile it for the non-Windows builds so it wouldn't...

Thanks for the info. I guess it would be fair to set -DSNAPPY_HAVE_BMI2=0 considering compilation of RocksDB itself does not use those instructions with PORTABLE=1.

We don't have proper data format versioning and therefore lack clear downgrade rules. It is one thing I hope to change soon. In the meantime the best chance for success...