public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/80223] RFE: Exclude functions from profile instrumentation Date: Tue, 07 Sep 2021 09:48:09 +0000 [thread overview] Message-ID: <bug-80223-4-OzOIuJEJB9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-80223-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80223 --- Comment #24 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:aad72d2ea8378e1a56c00d15daa4bdcac8a5ae39 commit r12-3379-gaad72d2ea8378e1a56c00d15daa4bdcac8a5ae39 Author: Martin Liska <mliska@suse.cz> Date: Tue Jun 22 10:09:01 2021 +0200 inline: do not einline when no_profile_instrument_function is different PR gcov-profile/80223 gcc/ChangeLog: * ipa-inline.c (can_inline_edge_p): Similarly to sanitizer options, do not inline when no_profile_instrument_function attributes are different in early inliner. It's fine to inline it after PGO instrumentation. gcc/testsuite/ChangeLog: * gcc.dg/no_profile_instrument_function-attr-2.c: New test.
next prev parent reply other threads:[~2021-09-07 9:48 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-80223-4@http.gcc.gnu.org/bugzilla/> 2021-06-14 20:46 ` ndesaulniers at google dot com 2021-06-14 21:22 ` i at maskray dot me 2021-06-15 19:04 ` i at maskray dot me 2021-06-17 18:16 ` ndesaulniers at google dot com 2021-06-18 23:42 ` ndesaulniers at google dot com 2021-06-21 8:37 ` marxin at gcc dot gnu.org 2021-06-21 17:41 ` ndesaulniers at google dot com 2021-06-21 18:45 ` marxin at gcc dot gnu.org 2021-06-21 18:51 ` i at maskray dot me 2021-06-21 19:11 ` ndesaulniers at google dot com 2021-06-22 18:56 ` ndesaulniers at google dot com 2021-06-23 11:55 ` marxin at gcc dot gnu.org 2021-06-23 17:07 ` i at maskray dot me 2021-06-23 19:09 ` elver at google dot com 2021-06-23 19:51 ` i at maskray dot me 2021-06-23 20:09 ` i at maskray dot me 2021-06-24 7:28 ` marxin at gcc dot gnu.org 2021-06-24 19:20 ` ndesaulniers at google dot com 2021-09-07 9:48 ` cvs-commit at gcc dot gnu.org [this message] 2021-09-07 9:49 ` marxin 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-80223-4-OzOIuJEJB9@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).