public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/103666] [11/12 Regression] compiling single-file programs with -fprofile-generate no longer leads to intended results since r11-627-g1dedc12d186a1108
Date: Tue, 04 Jan 2022 09:46:25 +0000	[thread overview]
Message-ID: <bug-103666-4-55y2domAL4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103666-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103666

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX
            Summary|[11/12 Regression]          |[11/12 Regression]
                   |compiling single-file       |compiling single-file
                   |preprocessed programs with  |programs with
                   |-fprofile-generate no       |-fprofile-generate no
                   |longer leads to intended    |longer leads to intended
                   |results since               |results since
                   |r11-627-g1dedc12d186a1108   |r11-627-g1dedc12d186a1108

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
that's because the explicitely named linker output in the -fprofile-use case. 
A fix might be to separate compile and link step.  I don't think there's
anything special about using preprocessed source:

> cat t.c
int main(){}
> ./xgcc -B. t.c -fprofile-generate
> ./a.out 
> ./xgcc -B. t.c -fprofile-use -o a.out-use
t.c: In function 'main':
t.c:1:1: warning: '/tmp/obj/gcc/a.out-use-t.gcda' profile count data file not
found [-Wmissing-profile]
    1 | int main(){}
      | ^~~
> ls *.gcda
a-t.gcda

I'd declare this as WONTFIX.  I've adjusted the C++ tester for tramp3d to use
an
explicit -dumpbase

      parent reply	other threads:[~2022-01-04  9:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-11 23:31 [Bug gcov-profile/103666] New: compiling single-file programs with -fprofile-generate no longer leads to intended results hubicka at gcc dot gnu.org
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 ` rguenth at gcc dot gnu.org [this message]

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-55y2domAL4@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).