public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/113765] New: autofdo: val-profiler-threads-1.c compilation, error: probability of edge from entry block not initialized Date: Mon, 05 Feb 2024 11:47:03 +0000 [thread overview] Message-ID: <bug-113765-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113765 Bug ID: 113765 Summary: autofdo: val-profiler-threads-1.c compilation, error: probability of edge from entry block not initialized Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: gcov-profile Assignee: unassigned at gcc dot gnu.org Reporter: andi-gcc at firstfloor dot org Target Milestone: --- With recent trunk (019dc63819be) When running the test suite on a Intel system with autofdo installed Executing on host: /home/ak/gcc/obj-full/gcc/xgcc -B/home/ak/gcc/obj-full/gcc/ /home/ak/gcc/gcc/gcc/testsuite/gcc.dg/tree-prof/val-profiler-threads-1.c -fdi agnostics-plain-output -O0 -pthread -fprofile-update=atomic -fauto-profile=/home/ak/gcc/obj-full/gcc/testsuite/gcc20/afdo.val-profiler-threads-1.gcda -DFOR_AU TOFDO_TESTING -fearly-inlining -dumpbase-ext .x02 -lm -o /home/ak/gcc/obj-full/gcc/testsuite/gcc20/val-profiler-threads-1.x02 (timeout = 300) spawn -ignore SIGHUP /home/ak/gcc/obj-full/gcc/xgcc -B/home/ak/gcc/obj-full/gcc/ /home/ak/gcc/gcc/gcc/testsuite/gcc.dg/tree-prof/val-profiler-threads-1.c -fdiag nostics-plain-output -O0 -pthread -fprofile-update=atomic -fauto-profile=/home/ak/gcc/obj-full/gcc/testsuite/gcc20/afdo.val-profiler-threads-1.gcda -DFOR_AUTOFD O_TESTING -fearly-inlining -dumpbase-ext .x02 -lm -o /home/ak/gcc/obj-full/gcc/testsuite/gcc20/val-profiler-threads-1.x02 /home/ak/gcc/gcc/gcc/testsuite/gcc.dg/tree-prof/val-profiler-threads-1.c: In function 'copy_memory': /home/ak/gcc/gcc/gcc/testsuite/gcc.dg/tree-prof/val-profiler-threads-1.c:13:7: error: probability of edge from entry block not initialized /home/ak/gcc/gcc/gcc/testsuite/gcc.dg/tree-prof/val-profiler-threads-1.c:13:7: error: probability of edge 2->4 not initialized /home/ak/gcc/gcc/gcc/testsuite/gcc.dg/tree-prof/val-profiler-threads-1.c:13:7: error: probability of edge 5->1 not initialized during GIMPLE pass: fixup_cfg /home/ak/gcc/gcc/gcc/testsuite/gcc.dg/tree-prof/val-profiler-threads-1.c:13:7: internal compiler error: verify_flow_info failed 0xafb91e verify_flow_info() ../../gcc/gcc/cfghooks.cc:287 0xf0e8a7 execute_function_todo ../../gcc/gcc/passes.cc:2100 0xf0edde execute_todo ../../gcc/gcc/passes.cc:2142 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. compiler exited with status 1 I'm not attaching the source because it also needs the autofdo gcov file to reproduce and the test case is already in tree.
next reply other threads:[~2024-02-05 11:47 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-05 11:47 andi-gcc at firstfloor dot org [this message] 2024-02-05 12:26 ` [Bug gcov-profile/113765] " andi-gcc at firstfloor dot org 2024-02-05 14:56 ` [Bug gcov-profile/113765] ICE: " rguenth at gcc dot gnu.org 2024-02-05 16:11 ` andi-gcc at firstfloor dot org 2024-02-06 8:41 ` [Bug gcov-profile/113765] [14 Regression] " rguenth at gcc dot gnu.org 2024-03-07 20:41 ` law at gcc dot gnu.org 2024-03-16 1:31 ` erozen at microsoft dot com 2024-03-26 10:54 ` rguenth at gcc dot gnu.org 2024-03-26 13:03 ` hubicka at gcc dot gnu.org 2024-03-26 20:49 ` erozen at microsoft dot com 2024-04-03 11:56 ` rguenth at gcc dot gnu.org 2024-04-04 0:31 ` cvs-commit at gcc dot gnu.org 2024-04-09 11:48 ` rguenth 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-113765-4@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).