From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-326293-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 25578 invoked by alias); 28 Jul 2010 18:18:18 -0000
Received: (qmail 25501 invoked by uid 48); 28 Jul 2010 18:18:04 -0000
Date: Wed, 28 Jul 2010 18:18:00 -0000
Subject: [Bug target/45111]  New: main function isn't profiled
X-Bugzilla-Reason: CC
Message-ID: <bug-45111-15155@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "ktietz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
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
X-SW-Source: 2010-07/txt/msg03125.txt.bz2

I recently noticed that for the main function the _monstartup call gets emitted
after _mcount call. This leads to the issue, that for the main function itself
no information are getting gathered.

A possible solution here would be to call mcount for main-function, if not
-mfentry is used, a second time. This shouldn't harm.

Any comments?


-- 
           Summary: main function isn't profiled
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ktietz at gcc dot gnu dot org
GCC target triplet: i?86-*-cygwin *-*-mingw*


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