* -fstack-usage and -flto the stack usage report is generated
[not found] <C2773327-9954-4877-9315-CF46111A91BD@microchip.com>
@ 2021-01-29 14:57 ` Visda.Vokhshoori
2021-02-01 8:19 ` Martin Liška
0 siblings, 1 reply; 3+ messages in thread
From: Visda.Vokhshoori @ 2021-01-29 14:57 UTC (permalink / raw)
To: gcc
Hello,
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.
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: -fstack-usage and -flto the stack usage report is generated
2021-01-29 14:57 ` -fstack-usage and -flto the stack usage report is generated Visda.Vokhshoori
@ 2021-02-01 8:19 ` Martin Liška
2021-02-01 17:13 ` Visda.Vokhshoori
0 siblings, 1 reply; 3+ messages in thread
From: Martin Liška @ 2021-02-01 8:19 UTC (permalink / raw)
To: Visda.Vokhshoori, gcc
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.
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
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: -fstack-usage and -flto the stack usage report is generated
2021-02-01 8:19 ` Martin Liška
@ 2021-02-01 17:13 ` Visda.Vokhshoori
0 siblings, 0 replies; 3+ messages in thread
From: Visda.Vokhshoori @ 2021-02-01 17:13 UTC (permalink / raw)
To: mliska, gcc
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-02-01 17:13 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <C2773327-9954-4877-9315-CF46111A91BD@microchip.com>
2021-01-29 14:57 ` -fstack-usage and -flto the stack usage report is generated Visda.Vokhshoori
2021-02-01 8:19 ` Martin Liška
2021-02-01 17:13 ` Visda.Vokhshoori
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).