From: Loreno Heer <loreno.heer@bluewin.ch>
To: Eli Zaretskii <eliz@gnu.org>, Andrea Corallo <akrl@sdf.org>
Cc: 58434@debbugs.gnu.org
Subject: bug#58434: Native compile results in error if -march and -mtune are specified
Date: Wed, 12 Oct 2022 09:13:34 +0200 [thread overview]
Message-ID: <5b3a7a2b-cb65-3458-2c44-efe64b414022@bluewin.ch> (raw)
In-Reply-To: <8335btej34.fsf@gnu.org>
>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: Loreno Heer <loreno.heer@bluewin.ch>, 58434@debbugs.gnu.org
>> Date: Tue, 11 Oct 2022 19:43:22 +0000
>>
>>> 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.
>
> OK, so I guess the only problem is that the compiler doesn't support
> "-march=native", and needs a specific architecture instead of a
> generic one.
Yes, but there might be some disadvantages of specifying the
architecture directly. For example cache sizes are not supplied.
(https://stackoverflow.com/questions/5470257/how-to-see-which-flags-march-native-will-activate?noredirect=1&lq=1)
next prev parent reply other threads:[~2022-10-12 7:13 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
2022-10-12 4:55 ` Eli Zaretskii
2022-10-12 7:13 ` Loreno Heer [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5b3a7a2b-cb65-3458-2c44-efe64b414022@bluewin.ch \
--to=loreno.heer@bluewin.ch \
--cc=58434@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.