================ @@ -6968,8 +6968,11 @@ defm unsigned : OptInFC1FFlag<"unsigned", "Enables UNSIGNED type">; def fno_automatic : Flag<["-"], "fno-automatic">, Group<f_Group>, HelpText<"Implies the SAVE attribute for non-automatic local objects in subprograms unless RECURSIVE">; -def fsave_main_program : Flag<["-"], "fsave-main-program">, Group<f_Group>, - HelpText<"Place all variables from the main program in static memory (otherwise scalars may be placed on the stack)">; +defm save_main_program : BoolOptionWithoutMarshalling<"f", "save-main-program", + PosFlag<SetTrue, [], [ClangOption], ---------------- tarunprabhu wrote:
Why is this a `ClangOption`? I am not saying that it is wrong, but it seems odd. I do see that the same has been done for the `ppc_native_vec_elem_order` option above also. What happens if the flag is passed to `clang` instead of `flang`? https://github.com/llvm/llvm-project/pull/124110 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits