From: Jeff Law <law@redhat.com>
To: Kamil Rytarowski <n54@gmx.com>, gcc-patches@sourceware.org
Subject: Re: [PATCH] Rearrange detection of temporary directory for NetBSD
Date: Wed, 25 Mar 2020 16:36:26 -0600 [thread overview]
Message-ID: <26075e9fdd6fbef40c5e5286914cde97efd5ecd5.camel@redhat.com> (raw)
In-Reply-To: <20200318192942.22006-1-n54@gmx.com>
On Wed, 2020-03-18 at 20:29 +0100, Kamil Rytarowski wrote:
> Set /tmp first, then /var/tmp. /tmp is volatile on NetBSD and
> /var/tmp not. This improves performance in the common use.
> The downstream copy of GCC was patched for this preference
> since 2015.
>
> Remove occurence of /usr/tmp as it was never valid for NetBSD.
> It was already activey disabled in the GCC manual page in 1996 and
> in the GCC source code at least in 1998.
>
> This change is not a matter of user-preference but Operating
> System defaults that disagree with the libiberty detection plan.
>
> No functional change for other Operataing Systems/environments.
>
> libiberty/ChangeLog:
>
> * make-temp-file.c (choose_tmpdir): Honor NetBSD specific paths.
> ---
> libiberty/ChangeLog | 4 ++++
> libiberty/make-temp-file.c | 8 +++++++-
> 2 files changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/libiberty/ChangeLog b/libiberty/ChangeLog
> index 106c107e91a..18b9357aaed 100644
> --- a/libiberty/ChangeLog
> +++ b/libiberty/ChangeLog
> @@ -1,3 +1,7 @@
> +2020-03-18 Kamil Rytarowski <n54@gmx.com>
> +
> + * make-temp-file.c (choose_tmpdir): Honor NetBSD specific paths.
I'd strongly recommend against this as-is.
The whole reason we prefer /var/tmp is because it's often dramatically larger
than a ram-backed /tmp.
I wouldn't mind dropping /usr/tmp. That so antiquated that it'd be non-
controversial. Can you send that as a separate patch.
Jeff
>
next prev parent reply other threads:[~2020-03-25 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 19:29 Kamil Rytarowski
2020-03-25 22:36 ` Jeff Law [this message]
2020-03-26 0:39 ` Kamil Rytarowski
2021-06-28 22:45 ` Gerald Pfeifer
2021-06-29 15:15 ` Jeff Law
2021-06-30 22:03 ` Gerald Pfeifer
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=26075e9fdd6fbef40c5e5286914cde97efd5ecd5.camel@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@sourceware.org \
--cc=n54@gmx.com \
/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).