public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/113646] PGO hurts run-time of 538.imagick_r as much as 68% at -Ofast -march=native Date: Mon, 29 Jan 2024 15:33:53 +0000 [thread overview] Message-ID: <bug-113646-4-IzNWQgUXWV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113646-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113646 --- Comment #2 from Jan Hubicka <hubicka at ucw dot cz> --- > Did you try with -fprofile-partial-training (is that default on? it probably > should ...). Can you please try training with the rate data instead of train It is not on by default - the problem of partial training is that it mostly nullifies any code size benefits from profile-use and that is relatively noticebale aspect of it in real-world situations (like for GCC itself or Firefox the overall size of binary matters). I need to work on this more, but now we have two-state optimize_size predicates and with level 1 we can turn off those -Os optimizations that make large tradeoffs of performance for size optimization. Honza > to rule out a mismatch?
next prev parent reply other threads:[~2024-01-29 15:33 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-28 21:31 [Bug gcov-profile/113646] New: " jamborm at gcc dot gnu.org 2024-01-29 8:27 ` [Bug gcov-profile/113646] " rguenth at gcc dot gnu.org 2024-01-29 15:33 ` hubicka at ucw dot cz [this message] 2024-01-31 14:45 ` jamborm at gcc dot gnu.org 2024-02-01 11:25 ` hubicka at ucw dot cz 2024-06-14 14:39 ` jamborm 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-113646-4-IzNWQgUXWV@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).