From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 1E8A5388CC02; Mon,  1 Feb 2021 17:08:22 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1E8A5388CC02
From: "Visda.vokhshoori at microchip dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/98922] New: -fstack-usage not working with -flto
Date: Mon, 01 Feb 2021 17:08:21 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: Visda.vokhshoori at microchip dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-98922-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2021 17:08:22 -0000

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

            Bug ID: 98922
           Summary: -fstack-usage not working with -flto
           Product: gcc
           Version: 8.3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
          Assignee: unassigned at gcc dot gnu.org
          Reporter: Visda.vokhshoori at microchip dot com
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

With link time optimization, -flto, the compiler doesn't print the stack us=
age
information to auxname.su file.=20

With -flto, the compiler dumps the stack usage of each function in
sourcfile/auxname.ltrans0.ltrans.su file.=20

However, maybe_unlink() in lto_wrapper.c removes all trans files, unless
--save-temps is specified.

To reproduce:=20=20
You can modify "gcc.dg/stack-usage-1.c": test case source to call foo() in
main(), and compile and link with flto and fstack-usage options, and scan f=
or {
dg-final { scan-stack-usage "foo\t\(0\)\tstatic" } }=20

The scan will fail.=