public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vesig34966 at estopg dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/96006] New: [GCOV] std::bind incorrectly marked as not executed
Date: Tue, 30 Jun 2020 14:41:10 +0000	[thread overview]
Message-ID: <bug-96006-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 96006
           Summary: [GCOV] std::bind incorrectly marked as not executed
           Product: gcc
           Version: 8.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: gcov-profile
          Assignee: unassigned at gcc dot gnu.org
          Reporter: vesig34966 at estopg dot com
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

$ cat repro.cpp
#include <functional>
#include <iostream>

void fn(int x) {
  std::cout << x << std::endl;
}

int main() {
  std::function<void()> fn2 = std::bind(
    fn, 2);
  fn2();


$ g++ -std=c++17 repro.cpp --coverage -o repro.o && ./repro.o && gcov repro.cpp
&& cat repro.cpp.gcov
...

        -:    0:Source:repro.cpp
        -:    0:Graph:repro.gcno
        -:    0:Data:repro.gcda
        -:    0:Runs:1
        -:    0:Programs:1
        -:    1:#include <functional>
        -:    2:#include <iostream>
        -:    3:
        1:    4:void fn(int x) {
        1:    5:  std::cout << x << std::endl;
        1:    6:}
        -:    7:
        1:    8:int main() {
    #####:    9:  std::function<void()> fn2 = std::bind(
        2:   10:    fn, 2);
        1:   11:  fn2();
        1:   12:}


Line #9 is wrongly marked as uncovered; line #10 is incorrectly marked as hit
twice.

$ gcc -v
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
8.4.0-1ubuntu1~18.04' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --disable-vtable-verify --enable-libmpx
--enable-plugin --enable-default-pie --with-system-zlib
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch
--disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.4.0 (Ubuntu 8.4.0-1ubuntu1~18.04)

             reply	other threads:[~2020-06-30 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30 14:41 vesig34966 at estopg dot com [this message]
2020-07-01  6:57 ` [Bug gcov-profile/96006] " 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-96006-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).