Options present in the initial release of libgccjit were handled using enums, whereas those added subsequently have their own per-option API entrypoints.
Adding entrypoints for each new option means that client code that use
the new options can be identified directly from binary metadata, which
would not be possible if we instead extended the various
enum gcc_jit_*_option.