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/102554] [10/11/12 Regression] Inlining missed at -O3 with non-default --param=early-inlining-insns and pragma optimize Date: Mon, 04 Oct 2021 06:53:05 +0000 [thread overview] Message-ID: <bug-102554-4-Vf072lu1VN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102554-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102554 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Target Milestone|--- |10.4 Summary|[ 10/11/12 Regresion ] |[10/11/12 Regression] |Inlining missed at -O3 with |Inlining missed at -O3 with |non-default |non-default |--param=early-inlining-insn |--param=early-inlining-insn |s and pragma optimize |s and pragma optimize Priority|P3 |P2 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- I suspect that the optimize() attribute resets the param value to its default. Martin - can you investigate / bisect?
next prev parent reply other threads:[~2021-10-04 6:53 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-01 15:52 [Bug ipa/102554] New: [ 10/11/12 Regresion ] " jschoen4 at gmail dot com 2021-10-04 6:53 ` rguenth at gcc dot gnu.org [this message] 2021-10-04 7:09 ` [Bug ipa/102554] [10/11 Regression] " marxin at gcc dot gnu.org 2021-10-04 14:05 ` jschoen4 at gmail dot com 2021-10-04 15:09 ` marxin at gcc dot gnu.org 2022-06-28 10:46 ` jakub at gcc dot gnu.org 2023-07-07 10:41 ` [Bug ipa/102554] [11 " rguenth 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-102554-4-Vf072lu1VN@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).