public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asharif at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/57115] New: Cannot merge separate single counters for function
Date: Mon, 29 Apr 2013 19:48:00 -0000	[thread overview]
Message-ID: <bug-57115-4@http.gcc.gnu.org/bugzilla/> (raw)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57115

             Bug #: 57115
           Summary: Cannot merge separate single counters for function
    Classification: Unclassified
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: gcov-profile
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: asharif@gcc.gnu.org


Created attachment 29975
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29975
source + .gcda file.

These files are from profiling WebKit.

To reproduce the error, run:

g++ -Werror -pthread -fno-exceptions -fno-strict-aliasing -Wall
-Wno-unused-parameter -Wno-missing-field-initializers -fvisibility=hidden -pipe
-fPIC -g -fno-strict-aliasing -O2 -fno-ident -fdata-sections
-ffunction-sections -g -Wno-c++0x-compat -fno-rtti -fno-threadsafe-statics
-fvisibility-inlines-hidden -Wsign-compare -fstack-protector-strong
-fprofile-use -fprofile-correction -o EventContext.o EventContext.ii

This was run on a system that defines TARGET_POSIX_IO so there shouldn't be a
problem writing profiles from multiple threads/processes, right?


             reply	other threads:[~2013-04-29 19:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-29 19:48 asharif at gcc dot gnu.org [this message]
2013-04-29 20:16 ` [Bug gcov-profile/57115] " pinskia 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-57115-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).