https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66657
--- Comment #6 from Andrew Pinski ---
(In reply to Kenneth Almquist from comment #3)
> (In reply to Andrew Pinski from comment #2)
> > What are you trying to do with the assembly after the fact?
>
> In this particular case, I wanted to look at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66657
--- Comment #4 from Andrew Pinski ---
You can use -save-temps and look at the .s files.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66657
--- Comment #5 from Andrew Pinski ---
You can use -save-temps and look at the .s files.
>To identify errant calls to printf and puts.
For this you can also do use the attribute warning and do it at compile time
rather than assembly time.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66657
--- Comment #3 from Kenneth Almquist kalmquist1 at hotmail dot com ---
(In reply to Andrew Pinski from comment #2)
What are you trying to do with the assembly after the fact?
In this particular case, I wanted to look at it for two reasons:
1)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66657
--- Comment #2 from Andrew Pinski pinskia at gcc dot gnu.org ---
What are you trying to do with the assembly after the fact?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66657
--- Comment #1 from Andrew Pinski pinskia at gcc dot gnu.org ---
There should be a gcc command line option to generate the assembly language
output of the lto compiler.
Use -save-temps.
