public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/103652] Producing profile with -O2 -flto and trying to consume it with -O3 -flto leads to ICEs on indirect call profiling Date: Mon, 13 Dec 2021 10:38:42 +0000 [thread overview] Message-ID: <bug-103652-4-sX3je8QvvD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103652-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103652 --- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> --- > You need to disable those to build multithreaded programs like clang. Well, I'm specifically speaking about: error: the control flow of function ‘BZ2_compressBlock’ does not match its profile data (counter ‘arcs’) this type of errors should not happen even in a multi-threaded programs. > I think you can produce testcase easily by making a function with one > indirect call for train run and many indirect calls in profile-use run. > > I have patch to avoid the buffer overflow - can send it after getting to > office. Sure, please send it.
next prev parent reply other threads:[~2021-12-13 10:38 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-10 16:18 [Bug gcov-profile/103652] New: " hubicka at gcc dot gnu.org 2021-12-13 9:53 ` [Bug gcov-profile/103652] " marxin at gcc dot gnu.org 2021-12-13 10:06 ` hubicka at kam dot mff.cuni.cz 2021-12-13 10:38 ` marxin at gcc dot gnu.org [this message] 2021-12-13 10:43 ` Jan Hubicka 2021-12-13 10:44 ` hubicka at kam dot mff.cuni.cz 2021-12-13 13:57 ` 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-103652-4-sX3je8QvvD@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).