public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH 0/3] Fix nonportable shell syntax in "test" and "[" commands
Date: Thu, 18 May 2023 13:56:44 +0100	[thread overview]
Message-ID: <20230518125647.2105203-1-jwakely@redhat.com> (raw)


Tested powerpc64le-linux.

I plan to push these as obvious, unless I hear objections.

Jonathan Wakely (2):
  gcc: Fix nonportable shell syntax in "test" and "[" commands
    [PR105831]
  contrib: Fix nonportable shell syntax in "test" and "[" commands
    [PR105831]

Michael Bäuerle (1):
  gcc: Fix nonportable shell syntax in "test" and "[" commands
    [PR105831]

 contrib/bench-stringop                               |  4 ++--
 contrib/reghunt/bin/reg-hunt                         |  2 +-
 contrib/repro_fail                                   |  4 ++--
 gcc/config.gcc                                       |  2 +-
 gcc/config/nvptx/gen-opt.sh                          |  2 +-
 gcc/configure                                        |  2 +-
 gcc/configure.ac                                     |  2 +-
 gcc/testsuite/gcc.test-framework/gen_directive_tests | 12 ++++++------
 8 files changed, 15 insertions(+), 15 deletions(-)

-- 
2.40.1


             reply	other threads:[~2023-05-18 12:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 12:56 Jonathan Wakely [this message]
2023-05-18 12:56 ` [PATCH 1/3] gcc: Fix nonportable shell syntax in "test" and "[" commands [PR105831] Jonathan Wakely
2023-05-18 13:00   ` Jakub Jelinek
2023-05-18 14:47   ` Bernhard Reutner-Fischer
2023-05-18 15:13     ` Jonathan Wakely
2023-05-18 12:56 ` [PATCH 2/3] " Jonathan Wakely
2023-05-18 12:59   ` Jakub Jelinek
2023-05-18 13:05     ` Jonathan Wakely
2023-05-18 13:03   ` [PATCH v2 " Jonathan Wakely
2023-05-18 13:15     ` Jakub Jelinek
2023-05-18 12:56 ` [PATCH 3/3] contrib: " Jonathan Wakely
2023-05-18 13:00   ` Jakub Jelinek

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=20230518125647.2105203-1-jwakely@redhat.com \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@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).