From: Andrea Corallo via "Emacs development discussions." <emacs-devel@gnu.org>
To: Arthur Miller <arthur.miller@live.com>
Cc: emacs-devel@gnu.org
Subject: Re: Q: What is default architecture for code produced by native compiler?
Date: Wed, 25 Aug 2021 07:36:59 +0000 [thread overview]
Message-ID: <xjftujec6w4.fsf@sdf.org> (raw)
In-Reply-To: <AM9PR09MB4977A934ED08F024C03F543296C69@AM9PR09MB4977.eurprd09.prod.outlook.com> (Arthur Miller's message of "Wed, 25 Aug 2021 04:49:57 +0200")
Arthur Miller <arthur.miller@live.com> writes:
> Andrea Corallo <akrl@sdf.org> writes:
>
>> Arthur Miller <arthur.miller@live.com> writes:
>>
>>> Just wonder, is it generic x86 or something later or does it uses
>>> native for architecture and cpu flags (-march=native and -mcpu=native)?
>>
>> I'd say is GCC's default.
>>
>>> If it is generic, do we have option to pass in arch and cpu flags?
>>
>> No we don't, even if we could expose it using
>> 'gcc_jit_context_add_command_line_option' for non obsolete versions of
>> GCC.
>>
>> Regards
>>
>> Andrea
> I am sorry to bother, but I have just seen:
>
> (defcustom native-comp-driver-options nil
> "Options passed verbatim to the native compiler's back-end driver.
> Note that not all options are meaningful; typically only the options
> affecting the assembler and linker are likely to be useful.
>
> Passing these options is only available in libgccjit version 9
> and above."
> :type '(repeat string) ; FIXME is this right?
> :version "28.1")
>
> I have tested with:
>
> (setq native-comp-driver-options '("-march=native" "-mcpu=native"))
>
> but I see no difference in emitted code when I dissaemble produced binaries.
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].
That said for most of the code we generate ATM I doubt would make much
difference to specify a different -march and/or -mcpu.
Regards
Andrea
[1] <https://gcc.gnu.org/onlinedocs/jit/topics/contexts.html>
next prev parent reply other threads:[~2021-08-25 7:36 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. [this message]
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
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=xjftujec6w4.fsf@sdf.org \
--to=emacs-devel@gnu.org \
--cc=akrl@sdf.org \
--cc=arthur.miller@live.com \
/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).