From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: arthur.miller@live.com, emacs-devel@gnu.org
Subject: Re: Q: What is default architecture for code produced by native compiler?
Date: Wed, 25 Aug 2021 16:11:51 +0300 [thread overview]
Message-ID: <83czq1vfc8.fsf@gnu.org> (raw)
In-Reply-To: <xjfpmu1d6au.fsf@sdf.org> (message from Andrea Corallo on Wed, 25 Aug 2021 13:04:25 +0000)
> 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.
next prev parent reply other threads:[~2021-08-25 13:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 19:29 Q: What is default architecture for code produced by native compiler? Arthur Miller
2021-08-24 20:11 ` Andrea Corallo via Emacs development discussions.
2021-08-25 1:13 ` Arthur Miller
2021-08-25 11:31 ` Eli Zaretskii
2021-08-25 23:26 ` Arthur Miller
2021-08-26 6:57 ` Eli Zaretskii
2021-08-26 8:02 ` martin rudalics
2021-08-26 8:16 ` Eli Zaretskii
2021-08-26 16:02 ` Arthur Miller
2021-08-26 16:29 ` Eli Zaretskii
2021-08-26 17:54 ` Arthur Miller
2021-08-26 15:59 ` Arthur Miller
2021-08-26 15:58 ` Arthur Miller
2021-08-26 16:27 ` Eli Zaretskii
2021-08-26 17:52 ` Arthur Miller
2021-08-25 2:49 ` Arthur Miller
2021-08-25 7:36 ` Andrea Corallo via Emacs development discussions.
2021-08-25 12:04 ` Eli Zaretskii
2021-08-25 13:04 ` Andrea Corallo via Emacs development discussions.
2021-08-25 13:11 ` Eli Zaretskii [this message]
2021-08-25 13:19 ` Andrea Corallo via Emacs development discussions.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83czq1vfc8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=akrl@sdf.org \
--cc=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).