public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "helohe at bluewin dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/107230] New: libgccjit rejects -march=native
Date: Wed, 12 Oct 2022 07:53:09 +0000 [thread overview]
Message-ID: <bug-107230-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107230
Bug ID: 107230
Summary: libgccjit rejects -march=native
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: jit
Assignee: dmalcolm at gcc dot gnu.org
Reporter: helohe at bluewin dot ch
Target Milestone: ---
Using the tutorial example 1 and adding
gcc_jit_context_add_command_line_option (ctxt, "-march=native");
gcc_jit_context_add_command_line_option (ctxt, "-mtune=native");
results in an error on both Mingw64 and Debian linux.
Bad value 'native' then valid options are listed which does include native
contradiction itself.
$ ./tut01-hello-world.exe
libgccjit.so: error: bad value 'native' for '-march=' switch
libgccjit.so: note: valid arguments to '-march=' switch are: nocona core2
nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell
core-avx2 broadwell skylake skylake-avx512 cannonlake icelake-client rocketlake
icelake-server cascadelake tigerlake cooperlake sapphirerapids alderlake
bonnell atom silvermont slm goldmont goldmont-plus tremont knl knm x86-64
x86-64-v2 x86-64-v3 x86-64-v4 eden-x2 nano nano-1000 nano-2000 nano-3000
nano-x2 eden-x4 nano-x4 k8 k8-sse3 opteron opteron-sse3 athlon64 athlon64-sse3
athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3 bdver4 znver1 znver2 znver3
btver1 btver2 native
Assembler messages:
Error: can't open C:\msys64\tmp\\libgccjit-123186/fake.s for reading: No such
file or directory
libgccjit.so: error: error invoking gcc driver
NULL result
next reply other threads:[~2022-10-12 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 7:53 helohe at bluewin dot ch [this message]
2023-05-19 1:25 ` [Bug jit/107230] " pinskia at gcc dot gnu.org
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=bug-107230-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.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.
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).