From: Andrea Corallo <akrl@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58434@debbugs.gnu.org, Loreno Heer <loreno.heer@bluewin.ch>
Subject: bug#58434: Native compile results in error if -march and -mtune are specified
Date: Tue, 11 Oct 2022 19:43:22 +0000 [thread overview]
Message-ID: <xjf5ygq16zp.fsf@ma.sdf.org> (raw)
In-Reply-To: <83lepme4so.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 11 Oct 2022 18:52:23 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> [Please use Reply All to keep the bug tracker on the CC list.]
>
>> Date: Tue, 11 Oct 2022 15:48:54 +0200
>> From: Loreno Heer <loreno.heer@bluewin.ch>
>>
>> (setq native-comp-compiler-options '("-O2" "-march=native" "-mtune=native"))
>>
>> in my .emacs file.
>> I wanted to speed up the installation a bit. I found the suggestion
>> here:
>> https://www.reddit.com/r/emacs/comments/prihh8/optimization_flags_for_nativecomp_whats_the/
>
> OK, so the compiler told you it doesn't support -march=native, so you
> will have to specify the exact architecture.
>
> Btw, I think you should use native-comp-driver-options for this, not
> native-comp-compiler-options. Andrea, am I right? I think GCC is
> "driver" and "compiler" means cc1, no? (If I'm right, we need to fix
> the doc strings.)
Hi Eli,
native-comp-driver-options is for assembler and linker while
native-comp-compiler-options is for the compiler. AFAIK 'march' affects
code generation so it should got to the compiler, then I believe the use
of native-comp-compiler-options here is correct.
Andrea
next prev parent reply other threads:[~2022-10-11 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 9:00 bug#58434: Native compile results in error if -march and -mtune are specified Loreno Heer
2022-10-11 13:40 ` Eli Zaretskii
[not found] ` <18231ac2-baca-e269-0f51-3c34e3283ea3@bluewin.ch>
2022-10-11 15:52 ` Eli Zaretskii
2022-10-11 18:58 ` Loreno Heer
2022-10-11 19:43 ` Andrea Corallo [this message]
2022-10-12 4:55 ` Eli Zaretskii
2022-10-12 7:13 ` Loreno Heer
2022-10-12 7:29 ` Eli Zaretskii
2022-10-12 10:35 ` Loreno Heer
2022-10-12 11:45 ` Andrea Corallo
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=xjf5ygq16zp.fsf@ma.sdf.org \
--to=akrl@sdf.org \
--cc=58434@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=loreno.heer@bluewin.ch \
/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).