public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111366] error: inlining failed in call to 'always_inline' 'hwy::PreventElision<int&>(int&)void': target specific option mismatch
Date: Tue, 12 Sep 2023 07:02:53 +0000	[thread overview]
Message-ID: <bug-111366-4-XzRXbprjZL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111366-4@http.gcc.gnu.org/bugzilla/>

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

Kewen Lin <linkw at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
         Resolution|INVALID                     |---
   Last reconfirmed|                            |2023-09-12
             Status|RESOLVED                    |REOPENED

--- Comment #12 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Kewen Lin from comment #9)
> It looks to me that the error message is expected, because the source code
> forces the function as always_inline, users would like it to be inlined
> always, it's compiled with -mcpu=power10 as pragma function target
> specifies, but the caller is compiled with -mcpu=power9 as command line
> specifies, the caller doesn't have the full ISA capability over the callee,
> it's unable to make inlining happen.

Sorry, I just realized that I misread the function which the pragma is applied
for (inverted the caller and the callee). It seems fine to make a caller with
-mcpu=power10 to inline a callee with -mcpu=power9, but unfortunately Power10
drops HTM capability, it causes the mismatch. The issue should be gone with an
extra -mno-htm.

This issue is similar to PR102059, whose fix already takes care of some cases
without actual htm feature uses. But it leaves inline asm alone, unfortunately
the reduced test case here is using inline asm. One idea is to enhance the fix
of PR102059 to further parse inline asm mnemonics.

  parent reply	other threads:[~2023-09-12  7:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11  8:08 [Bug target/111366] New: " malat at debian dot org
2023-09-11  8:08 ` [Bug target/111366] " malat at debian dot org
2023-09-11  8:10 ` malat at debian dot org
2023-09-11  8:11 ` malat at debian dot org
2023-09-11  8:15 ` malat at debian dot org
2023-09-11 11:08 ` jan.wassenberg at gmail dot com
2023-09-11 12:04 ` jan.wassenberg at gmail dot com
2023-09-11 12:46 ` malat at debian dot org
2023-09-11 12:58 ` malat at debian dot org
2023-09-12  3:00 ` linkw at gcc dot gnu.org
2023-09-12  3:14 ` linkw at gcc dot gnu.org
2023-09-12  6:03 ` malat at debian dot org
2023-09-12  7:02 ` linkw at gcc dot gnu.org [this message]
2023-09-12  7:09 ` linkw at gcc dot gnu.org
2023-09-12  7:52 ` linkw at gcc dot gnu.org
2023-09-14 14:19 ` malat at debian dot org
2023-09-14 14:40 ` malat at debian dot org
2023-09-15  2:02 ` linkw at gcc dot gnu.org
2023-09-15  6:41 ` jan.wassenberg at gmail dot com
2023-09-25  5:31 ` cvs-commit at gcc dot gnu.org
2023-10-16  2:07 ` cvs-commit at gcc dot gnu.org
2023-10-16  2:09 ` cvs-commit at gcc dot gnu.org
2023-10-16  3:33 ` linkw 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-111366-4-XzRXbprjZL@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).