public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Peter Foley <pefoley2@pefoley.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v2] configure: Only create serdep.tmp if needed
Date: Mon, 16 Jan 2023 18:14:09 -0700	[thread overview]
Message-ID: <a3cd3270-9e45-d92f-03b1-7ebe3fa43680@gmail.com> (raw)
In-Reply-To: <20230117011203.3342271-1-pefoley2@pefoley.com>



On 1/16/23 18:12, Peter Foley wrote:
> There's no reason to create this file if none of the serial configure
> options are passed.
> 
> v2: Use test instead of [ to avoid running afoul of autoconf quoting.
> 
> ChangeLog:
> 
> 	* configure: Regenerate.
> 	* configure.ac: Only create serdep.tmp if needed
Note I think this should be deferred to gcc-14 given that gcc-13 is in 
regression bugfixes only stage right now.

jeff

  reply	other threads:[~2023-01-17  1:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-15  5:58 [PATCH] " Peter Foley
2023-01-17  1:12 ` [PATCH v2] " Peter Foley
2023-01-17  1:14   ` Jeff Law [this message]
2023-04-21 19:16   ` Jeff Law

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=a3cd3270-9e45-d92f-03b1-7ebe3fa43680@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=pefoley2@pefoley.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).