From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-149810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 25360 invoked by alias); 11 Jul 2005 05:14:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 25339 invoked by uid 48); 11 Jul 2005 05:14:17 -0000
Date: Mon, 11 Jul 2005 05:14:00 -0000
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Message-ID: <20050711051415.22401.pinskia@gcc.gnu.org>
Reply-To: gcc-bugzilla@gcc.gnu.org
Subject: [Bug tree-optimization/22401] New: DOM messes up the profiling info
X-Bugzilla-Reason: CC
X-SW-Source: 2005-07/txt/msg01233.txt.bz2
List-Id: <gcc-bugs.sourceware.org>

Take the following simple example loop:
void __show_backtrace(void *rw)
{
  while(rw);
}

We get invalid warnings in the tree dumps about profiling info being wrong:
__show_backtrace (rw)
{
<L3>:;
  if (rw_1 != 0B) goto <L0>; else goto <L2>;

Invalid sum of incoming frequencies 9879, should be 8900
<L0>:;
  goto <bb 1> (<L0>);

Invalid sum of incoming frequencies 121, should be 1100
<L2>:;
  return;

}

I am filing this because for 4.2, I hear that the rtl level profiling info will be coming from the tree level 
(after loop.c is removed).

-- 
           Summary: DOM messes up the profiling info
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pinskia at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org,law at gcc dot gnu dot
                    org


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