public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schuchart at icl dot utk.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/66594] jitted code should use -mtune=native
Date: Wed, 24 May 2023 18:13:06 +0000	[thread overview]
Message-ID: <bug-66594-4-sAJ411eYsD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66594-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66594

Joseph <schuchart at icl dot utk.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |schuchart at icl dot utk.edu

--- Comment #10 from Joseph <schuchart at icl dot utk.edu> ---
The lack of target-specific optimizations is biting us quite a bit and manually
specifying an architecture is not really an option, unless we duplicate the
detection mechanism of GCC, which is not ideal. I am not familiar with the GCC
code base and from the discussion below it's not clear what would be needed to
advance this. If someone could provide some hints on what is missing and
how/where it could be implemented we could probably take a stab at it. 

Would it be sufficient to add a macro to the header of the targets (as
suggested here https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66594#c6) that
provide host_detect_local_cpu and ignore the ones that do not provide it? Or
would it be better to hard-code calls for the architectures that provide them,
like in the referenced patch but with architecture-specific pre-processor
guards? We mostly care about i386 and arm/aarch64 but covering all available
bases would be necessary, I guess.

      parent reply	other threads:[~2023-05-24 18:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19  1:28 [Bug jit/66594] New: " dmalcolm at gcc dot gnu.org
2015-06-19  1:39 ` [Bug jit/66594] " pinskia at gcc dot gnu.org
2015-06-19 16:20 ` dmalcolm at gcc dot gnu.org
2015-06-19 16:21 ` dmalcolm at gcc dot gnu.org
2015-06-19 16:30 ` ktkachov at gcc dot gnu.org
2015-06-19 17:12 ` dmalcolm at gcc dot gnu.org
2015-06-19 17:15 ` dmalcolm at gcc dot gnu.org
2023-05-19  1:25 ` pinskia at gcc dot gnu.org
2023-05-24 18:13 ` schuchart at icl dot utk.edu [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=bug-66594-4-sAJ411eYsD@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).