From: Tom Tromey <tom@tromey.com>
To: Ben Boeckel via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Ben Boeckel <ben.boeckel@kitware.com>,
gcc@gcc.gnu.org, brad.king@kitware.com, fortran@gcc.gnu.org,
anlauf@gmx.de, nathan@acm.org
Subject: Re: [PATCH v2 3/3] p1689r5: initial support
Date: Tue, 01 Nov 2022 08:57:37 -0600 [thread overview]
Message-ID: <87sfj290ym.fsf@tromey.com> (raw)
In-Reply-To: <20221027231645.67623-4-ben.boeckel@kitware.com> (Ben Boeckel via Gcc-patches's message of "Thu, 27 Oct 2022 19:16:44 -0400")
>>>>> "Ben" == Ben Boeckel via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
Ben> - `-fdeps-file=` specifies the path to the file to write the format to.
I don't know how this output is intended to be used, but one mistake
made with the other dependency-tracking options was that the output file
isn't created atomically. As a consequence, Makefiles normally have to
work around this to be robust. If that's a possible issue here then it
would be best to handle it in this patch.
Tom
next prev parent reply other threads:[~2022-11-01 14:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 23:16 [PATCH v2 0/1] RFC: P1689R5 support Ben Boeckel
2022-10-27 23:16 ` [PATCH v2 1/3] libcpp: reject codepoints above 0x10FFFF Ben Boeckel
2022-10-28 12:54 ` David Malcolm
2022-11-07 23:04 ` Jason Merrill
2022-10-27 23:16 ` [PATCH v2 2/3] libcpp: add a function to determine UTF-8 validity of a C string Ben Boeckel
2022-10-28 12:59 ` David Malcolm
2022-10-28 17:14 ` Ben Boeckel
2022-11-07 23:47 ` Jason Merrill
2022-10-27 23:16 ` [PATCH v2 3/3] p1689r5: initial support Ben Boeckel
2022-10-28 17:15 ` Ben Boeckel
2022-11-01 14:57 ` Tom Tromey [this message]
2022-11-01 16:22 ` Ben Boeckel
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=87sfj290ym.fsf@tromey.com \
--to=tom@tromey.com \
--cc=anlauf@gmx.de \
--cc=ben.boeckel@kitware.com \
--cc=brad.king@kitware.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=nathan@acm.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).