public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
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 [thread overview] Message-ID: <bug-98922-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98922 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 usage information to auxname.su file. With -flto, the compiler dumps the stack usage of each function in sourcfile/auxname.ltrans0.ltrans.su file. However, maybe_unlink() in lto_wrapper.c removes all trans files, unless --save-temps is specified. To reproduce: 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 for { dg-final { scan-stack-usage "foo\t\(0\)\tstatic" } } The scan will fail.
next reply other threads:[~2021-02-01 17:08 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-01 17:08 Visda.vokhshoori at microchip dot com [this message] 2021-02-02 8:20 ` [Bug lto/98922] " rguenth at gcc dot gnu.org 2021-02-02 13:11 ` marxin at gcc dot gnu.org 2021-02-04 14:42 ` Visda.vokhshoori at microchip dot com
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-98922-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: linkBe 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).