public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/114784] [14 Regression] Inlining fails for always_inline inheriting constructor Date: Mon, 22 Apr 2024 11:14:14 +0000 [thread overview] Message-ID: <bug-114784-4-Mkpd3Cc8Ze@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114784-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114784 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 58006 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58006&action=edit gcc14-pr114784.patch Adjusted patch. maybe_clone_body currently copies DECL_DISREGARD_INLINE_LIMITS, DECL_DLLIMPORT_P and DECL_VISIBILITY*, should those be copied too? And shouldn't some from the above list be copied in both places?
next prev parent reply other threads:[~2024-04-22 11:14 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-19 20:05 [Bug ipa/114784] New: " dani at danielbertalan dot dev 2024-04-19 20:08 ` [Bug ipa/114784] " dani at danielbertalan dot dev 2024-04-19 20:21 ` jakub at gcc dot gnu.org 2024-04-19 20:42 ` jakub at gcc dot gnu.org 2024-04-19 21:07 ` jakub at gcc dot gnu.org 2024-04-19 22:00 ` dani at danielbertalan dot dev 2024-04-22 11:14 ` jakub at gcc dot gnu.org [this message] 2024-04-23 6:39 ` cvs-commit at gcc dot gnu.org 2024-04-23 6:40 ` jakub 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-114784-4-Mkpd3Cc8Ze@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).