can you support g++ instead of clang++ only

[ZhiganZ]

[azimafroozeh]

Thanks for the suggestion!

We currently use Clang as the only supported compiler because, in our evaluations, it provided more consistent and predictable autovectorization behavior compared to GCC. This consistency is critical for FastLanes, since much of its performance depends on compiler-optimized vectorized loops — as detailed in our VLDB 2023 paper “The FastLanes Compression Layout: Decoding >100 Billion Integers per Second with Scalar Code”

For that reason, we’d like to keep Clang as the sole supported compiler for now.

We might revisit GCC support in the future if it reaches comparable autovectorization performance or if there is a serious need to support it.

[sounkou-bioinfo]

Thanks for the suggestion!

We currently use Clang as the only supported compiler because, in our evaluations, it provided more consistent and predictable autovectorization behavior compared to GCC. This consistency is critical for FastLanes, since much of its performance depends on compiler-optimized vectorized loops — as detailed in our VLDB 2023 paper “The FastLanes Compression Layout: Decoding >100 Billion Integers per Second with Scalar Code”

For that reason, we’d like to keep Clang as the sole supported compiler for now.

We might revisit GCC support in the future if it reaches comparable autovectorization performance or if there is a serious need to support it.

A Serious R (reader and writer) binding would not be possible without GCC support and i guess conversion ops would require containers in most linux systems