On 2017-10-06 15:00, Dennis Lee Bieber <wlfr...@ix.netcom.com> wrote:
> On Fri, 6 Oct 2017 15:04:45 +0100, bartc <b...@freeuk.com> declaimed the
> following:
>>But if I use the -S option (show assembly listing) that DOES output to a
>>file (program.s).
>>
>
> The assembler file is created anyway -- but is normally a temporary
> file, deleted after the assembly pass of gcc. The -S option tells gcc to
> /stop before the assembly pass/, leaving the assembly file in the
> directory.
On modern gcc, no: The assembly file is normally created in /tmp or
(with -pipe) not at all. With -S the assembly file needs to be created
with the proper name in the current directory, which is not the default
behaviour.
Your description may have been true for the original portable c
compiler. But if I remember correctly, that one also wrote the output of
the preprocessor to a temporary file which was then read by cc1.
In any case, that -E writes to stdout and -S to file is an inconsistency
which looks more like a historical accident than a planned feature to
me.
hp
--
_ | Peter J. Holzer | Fluch der elektronischen Textverarbeitung:
|_|_) | | Man feilt solange an seinen Text um, bis
| | | h...@hjp.at | die Satzbestandteile des Satzes nicht mehr
__/ | http://www.hjp.at/ | zusammenpaßt. -- Ralph Babel
--
https://mail.python.org/mailman/listinfo/python-list
