From: David Malcolm <dmalcolm@redhat.com>
To: "Li, Yicheng" <yli137@vols.utk.edu>, "jit@gcc.gnu.org" <jit@gcc.gnu.org>
Subject: Re: "march=native" flag not working in libgccjit
Date: Mon, 15 May 2023 17:34:57 -0400 [thread overview]
Message-ID: <4b3aae60d9bb71debc753f6c091bd441ab47137f.camel@redhat.com> (raw)
In-Reply-To: <44CD6A9D-15EE-4E9F-8521-B1B0EC0F33F4@vols.utk.edu>
On Mon, 2023-05-15 at 20:07 +0000, Li, Yicheng via Jit wrote:
> Hi,
>
> In libjitgcc, I created a function and set flags “march=native” with
> gcc_jit_context_add_command_line_option( ctxt, “-march=native”.
> However, the error is below:
>
> 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 emeraldrapids alderlake raptorlake
> meteorlake graniterapids bonnell atom silvermont slm goldmont
> goldmont-plus tremont sierraforest grandridge 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 lujiazui k8 k8-sse3 opteron opteron-sse3
> athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2
> bdver3 bdver4 znver1 znver2 znver3 znver4 btver1 btver2 native
Sorry about this; this is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66594
and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107230
Unfortunately it's tricky to implement this within libgccjit due to the
differences between it and the normal command-line way of invoking gcc.
If someone wants to try fixing this, that would be great.
Dave
prev parent reply other threads:[~2023-05-15 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 20:07 Li, Yicheng
2023-05-15 21:34 ` David Malcolm [this message]
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=4b3aae60d9bb71debc753f6c091bd441ab47137f.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=jit@gcc.gnu.org \
--cc=yli137@vols.utk.edu \
/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).