public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/103666] New: compiling single-file programs with -fprofile-generate no longer leads to intended results
Date: Sat, 11 Dec 2021 23:31:07 +0000 [thread overview]
Message-ID: <bug-103666-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103666
Bug ID: 103666
Summary: compiling single-file programs with -fprofile-generate
no longer leads to intended results
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: gcov-profile
Assignee: unassigned at gcc dot gnu.org
Reporter: hubicka at gcc dot gnu.org
CC: marxin at gcc dot gnu.org
Target Milestone: ---
The following should work but we fail to name the gcda file same way in both
builds:
jh@ryzen3:~> ~/trunk-install/bin/g++ -Ofast -march=native -fprofile-generate
tramp3d-v44.ii -fpermissive -std=c++03
jh@ryzen3:~> ./a.out -n 5
jh@ryzen3:~> ~/trunk-install/bin/g++ -Ofast -march=native -fprofile-use
tramp3d-v44.ii -fpermissive -std=c++03 -o a.out-use
/aux/hubicka/tramp3d-v4b.cpp: In function ‘(static initializers for
/aux/hubicka/tramp3d-v4b.cpp)’:
/aux/hubicka/tramp3d-v4b.cpp:56088:1: warning:
‘/home/jh/a.out-use-tramp3d-v44.gcda’ profile count data file not found
[-Wmissing-profile]
next reply other threads:[~2021-12-11 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 23:31 hubicka at gcc dot gnu.org [this message]
2021-12-13 10:27 ` [Bug gcov-profile/103666] [11/12 Regression] compiling single-file preprocessed programs with -fprofile-generate no longer leads to intended results since r11-627-g1dedc12d186a1108 marxin at gcc dot gnu.org
2021-12-15 11:29 ` pinskia at gcc dot gnu.org
2022-01-04 9:46 ` [Bug gcov-profile/103666] [11/12 Regression] compiling single-file " 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-103666-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: link
Be 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).