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 c++/100686] attribute optimize ("O2") doesn't inline lambda Date: Thu, 20 May 2021 06:40:03 +0000 [thread overview] Message-ID: <bug-100686-4-4ia6rODVIw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100686-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100686 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|middle-end |c++ --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Likely nested functions (aka lambdas in this case) do not inherit attributes (and in this case in particular optimize attributes) from the containing function. That might be by design and correct, using the #pragma variant should result in more obvious behavior here (I hope ;)). So I'm not sure if this is a bug, esp. in the context of C nested functions, but of course the C++ FE could decide it is and apply select attributes also to lambdas contained in a function.
prev parent reply other threads:[~2021-05-20 6:40 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-19 17:20 [Bug middle-end/100686] New: " msebor at gcc dot gnu.org 2021-05-20 6:40 ` rguenth at gcc dot gnu.org [this message]
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-100686-4-4ia6rODVIw@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).