public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: <Visda.Vokhshoori@microchip.com>
To: <mliska@suse.cz>, <gcc@gcc.gnu.org>
Subject: Re: -fstack-usage and -flto the stack usage report is generated
Date: Mon, 1 Feb 2021 17:13:35 +0000	[thread overview]
Message-ID: <BD4873C7-926A-4C2A-BC9C-79AB62C9B4B3@microchip.com> (raw)
In-Reply-To: <8a165e4f-7cc4-9421-0c03-1fc917050152@suse.cz>

On 2021-02-01, 3:19 AM, "Martin Liška" <mliska@suse.cz> wrote:

    EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe

    On 1/29/21 3:57 PM, Visda.Vokhshoori--- via Gcc wrote:
    >
    > Hello,

    Hi.

    >
    > With link time optimization the stack usage information is determined during local transformation and written to program.ltrans0.ltrans.su.  There will be one .su file for each partition.
    >
    > All ltrans files, including the .su, are removed unless –save-temps is indicated.
    >
    > Although not obvious/not documented, but I am assuming this is working as designed.  Developers should include –save-temps along with -fstack-suage and -flto.

    >>Thank you for the report. It seems it's a bug, please report it to bugzilla.

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

    >>Martin

    >
    > Or is this a bug?  That is exception should be made for the ltrans.su files and they should be kept around regardless.
    >
    > Thanks,
    > Visda
    >

Thanks,
Visda


      reply	other threads:[~2021-02-01 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C2773327-9954-4877-9315-CF46111A91BD@microchip.com>
2021-01-29 14:57 ` Visda.Vokhshoori
2021-02-01  8:19   ` Martin Liška
2021-02-01 17:13     ` Visda.Vokhshoori [this message]

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=BD4873C7-926A-4C2A-BC9C-79AB62C9B4B3@microchip.com \
    --to=visda.vokhshoori@microchip.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mliska@suse.cz \
    /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).