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 03:14:10 +0000	[thread overview]
Message-ID: <bug-111366-4-dcCO6C4Nv5@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

--- Comment #10 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Jan Wassenberg from comment #5)
> Thanks for reporting this. One might think this is caused by -mcpu=power9
> clashing with our #pragma target altivec,vsx,power8-vector.
> 
> However, what makes this seem like an actual bug is that -flto=auto is
> additionally required to trigger the bug.

This reminds me there is one bug in the current function rs6000_can_inline_p,
see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102059#c17

-flto=auto makes the callee have a constructed DECL_FUNCTION_SPECIFIC_TARGET,
so callee_tree is not NULL, it would further check ISA flags. Without it, the
current implementation doesn't adopt the default option node and just ignore it
unexpectedly. Filed PR111380.

  parent reply	other threads:[~2023-09-12  3:14 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 [this message]
2023-09-12  6:03 ` malat at debian dot org
2023-09-12  7:02 ` linkw at gcc dot gnu.org
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-dcCO6C4Nv5@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).