public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/102059] Incorrect always_inline diagnostic in LTO mode with #pragma GCC target("cpu=power10") Date: Thu, 26 Aug 2021 08:24:25 +0000 [thread overview] Message-ID: <bug-102059-4-pozWvuUHz8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102059-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102059 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hubicka at gcc dot gnu.org --- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> --- Note that x86 uses for example else if (caller_opts->x_ix86_fpmath != callee_opts->x_ix86_fpmath /* If the calle doesn't use FP expressions differences in ix86_fpmath can be ignored. We are called from FEs for multi-versioning call optimization, so beware of ipa_fn_summaries not available. */ && (! ipa_fn_summaries || ipa_fn_summaries->get (callee_node) == NULL || ipa_fn_summaries->get (callee_node)->fp_expressions)) ret = false; I wonder if we need to give targets the ability to compute IPA inline summary bits, like "uses HTM" or "uses intrinsics for ISA X", to selectively ignore bits that are not actually used. And as always my stance on "always_inline" is that we should give thumbs up to inlining and let the user shoot itself in the foot if he likes to.
next prev parent reply other threads:[~2021-08-26 8:24 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-25 9:42 [Bug lto/102059] New: " fw at gcc dot gnu.org 2021-08-25 9:49 ` [Bug ipa/102059] " rguenth at gcc dot gnu.org 2021-08-25 9:54 ` marxin at gcc dot gnu.org 2021-08-25 11:49 ` chip.kerchner at ibm dot com 2021-08-25 13:25 ` marxin at gcc dot gnu.org 2021-08-25 13:30 ` marxin at gcc dot gnu.org 2021-08-25 13:34 ` marxin at gcc dot gnu.org 2021-08-25 13:44 ` marxin at gcc dot gnu.org 2021-08-25 15:34 ` linkw at gcc dot gnu.org 2021-08-26 6:26 ` linkw at gcc dot gnu.org 2021-08-26 8:20 ` rguenth at gcc dot gnu.org 2021-08-26 8:24 ` rguenth at gcc dot gnu.org [this message] 2021-08-26 8:34 ` fw at gcc dot gnu.org 2021-08-26 8:45 ` linkw at gcc dot gnu.org 2021-08-26 8:56 ` linkw at gcc dot gnu.org 2021-08-26 9:02 ` linkw at gcc dot gnu.org 2021-08-26 9:04 ` marxin at gcc dot gnu.org 2021-08-26 9:29 ` linkw at gcc dot gnu.org 2021-08-26 9:34 ` linkw at gcc dot gnu.org 2021-08-26 18:46 ` meissner at gcc dot gnu.org 2021-09-01 7:10 ` linkw at gcc dot gnu.org 2021-09-14 14:09 ` chip.kerchner at ibm dot com 2021-09-14 14:11 ` chip.kerchner at ibm dot com 2021-09-15 9:57 ` linkw at gcc dot gnu.org 2021-09-15 12:19 ` chip.kerchner at ibm dot com 2021-11-26 2:07 ` linkw at gcc dot gnu.org 2022-01-05 3:26 ` cvs-commit at gcc dot gnu.org 2022-02-04 18:55 ` pc at gcc dot gnu.org 2022-02-04 19:33 ` dan at danny dot cz 2022-02-04 20:15 ` bergner at gcc dot gnu.org 2022-02-05 2:50 ` linkw at gcc dot gnu.org 2022-02-08 21:53 ` meissner at gcc dot gnu.org 2022-02-09 2:33 ` linkw at gcc dot gnu.org 2022-02-09 3:20 ` linkw at gcc dot gnu.org 2022-02-09 7:21 ` rguenth at gcc dot gnu.org 2022-02-09 7:35 ` linkw at gcc dot gnu.org 2022-03-15 6:38 ` linkw at gcc dot gnu.org 2022-05-05 18:14 ` bergner at gcc dot gnu.org 2022-05-06 16:41 ` cvs-commit at gcc dot gnu.org 2022-05-06 19:03 ` cvs-commit at gcc dot gnu.org 2022-05-06 21:45 ` cvs-commit at gcc dot gnu.org 2022-05-19 21:20 ` cvs-commit at gcc dot gnu.org 2022-05-19 21:25 ` bergner 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-102059-4-pozWvuUHz8@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: linkBe 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).