From: Loreno Heer <loreno.heer@bluewin.ch>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58434@debbugs.gnu.org, akrl@sdf.org
Subject: bug#58434: Native compile results in error if -march and -mtune are specified
Date: Wed, 12 Oct 2022 12:35:38 +0200 [thread overview]
Message-ID: <8c6f532b-35bc-d221-22e7-e37484137be0@bluewin.ch> (raw)
In-Reply-To: <83leplcxeb.fsf@gnu.org>
You are right, did not notice this is a gccjit issue. I filed a bug
report with the gcc people. (might also be a packaging problem on mingw
and debian, that I don't know)
On 12.10.2022 09:29, Eli Zaretskii wrote:
>> Date: Wed, 12 Oct 2022 09:13:34 +0200
>> Cc: 58434@debbugs.gnu.org
>> From: Loreno Heer <loreno.heer@bluewin.ch>
>>
>>> 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)
>
> What can Emacs do about this? The problem seems to be between you and
> libgccjit/GCC you have installed. The rejection comes from there, not
> from Emacs, AFAIU.
next prev parent reply other threads:[~2022-10-12 10:35 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
2022-10-12 7:29 ` Eli Zaretskii
2022-10-12 10:35 ` Loreno Heer [this message]
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=8c6f532b-35bc-d221-22e7-e37484137be0@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.