Re: Q: What is default architecture for code produced by native compiler?

[Eli Zaretskii]

> From: Andrea Corallo <akrl@sdf.org>
> Cc: arthur.miller@live.com, emacs-devel@gnu.org
> Date: Wed, 25 Aug 2021 13:04:25 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> Driver options are not for the compiler but rather linker and assembler,
> >> infact `native-comp-driver-options' relies on
> >> 'gcc_jit_context_add_driver_option' [1].
> >
> > Then the name of the defcustom is misleading, IMO.
> 
> You are probably right, the defcustom name is inherited from the
> libgccjit entry point name but it is probably not optimal.  Any
> suggestion for a better one?

Something like native-comp-backend-driver-options, together with
explaining in the doc string that typically only assembler and linker
options are meaningful.

> So yes, exposing 'gcc_jit_context_add_command_line_option' we could.

We probably should, yes.

Thanks.