public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tejohnson at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/63443] New: copyrename2 introducing bogus profile counts
Date: Thu, 02 Oct 2014 16:10:00 -0000	[thread overview]
Message-ID: <bug-63443-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 63443
           Summary: copyrename2 introducing bogus profile counts
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tejohnson at google dot com

This problem showed up in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63422,
where a new assert introduced in jump threading triggered because of insane
profile counts coming in. The LTO test case attached to that bug has profile
data, but the affected routine did not have profile counts and only frequencies
(main() from mozilla-xremote-client.ii which does not have a gcda file).
However, copyrename2 introduced some non-zero profile counts, which should not
happen.

To duplicate:
% g++ -flto -fprofile-use -fno-exceptions -std=gnu++0x -O2
mozilla-xremote-client.ii XRemoteClient.ii

I've attached the input files to this bug report as well.


                 reply	other threads:[~2014-10-02 16:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-63443-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).