From: "Arsen Arsenović" <arsen@aarsen.me>
To: Florian Weimer <fweimer@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Triggering -save-temps from the front-end code
Date: Mon, 28 Nov 2022 14:02:28 +0100 [thread overview]
Message-ID: <86edtnjkln.fsf@aarsen.me> (raw)
In-Reply-To: <87y1rvs4gd.fsf@oldenburg.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
Hi,
Florian Weimer via Gcc <gcc@gcc.gnu.org> writes:
> Unfortunately, some build systems immediately delete the input source
> files. Is there some easy way I can dump the pre-processed and
> non-preprocessed sources to my log file? I tried to understand how
> -save-temps for crash recovery works, but it seems that this runs
> outside of the frontend, in the driver.
Would dumping unconditionally into some "side channel" -dumpdir be a
sufficient workaround?
https://gcc.gnu.org/onlinedocs/gcc-12.2.0/gcc/Overall-Options.html#index-dumpdir
Hope that helps, have a great day.
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]
next prev parent reply other threads:[~2022-11-28 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 11:28 Florian Weimer
2022-11-28 11:44 ` Richard Biener
2022-11-28 13:02 ` Arsen Arsenović [this message]
2022-11-28 13:14 ` Florian Weimer
2022-11-28 17:18 ` Marc Glisse
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=86edtnjkln.fsf@aarsen.me \
--to=arsen@aarsen.me \
--cc=fweimer@redhat.com \
--cc=gcc@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: 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).