public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: YunQiang Su <syq@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-8500] MIPS: Fix typo in gcc/configure.ac: gcc_cv_as_mips_explicit
Date: Mon, 29 Jan 2024 16:32:25 +0000 (GMT)	[thread overview]
Message-ID: <20240129163226.0DCC83858430@sourceware.org> (raw)

https://gcc.gnu.org/g:8e84b4fad149b9b9544c7b1fc61a45cf6139176e

commit r14-8500-g8e84b4fad149b9b9544c7b1fc61a45cf6139176e
Author: YunQiang Su <syq@gcc.gnu.org>
Date:   Tue Jan 30 00:26:28 2024 +0800

    MIPS: Fix typo in gcc/configure.ac: gcc_cv_as_mips_explicit
    
    gcc_cv_as_mips_explicit should be gcc_cv_as_mips_explicit_relocs.
    This was introduced in commit
    58af788d1d0825187def434c95cab35a690a31b0.
    
    gcc
            PR target/113655
            * configure.ac: Fix typo gcc_cv_as_mips_explicit should be
            gcc_cv_as_mips_explicit_relocs.
            * configure: Regnerated.

Diff:
---
 gcc/configure    | 2 +-
 gcc/configure.ac | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/configure b/gcc/configure
index 578c72da70af..c83e09beea9f 100755
--- a/gcc/configure
+++ b/gcc/configure
@@ -30417,7 +30417,7 @@ fi
 
     fi
 
-    if test x$gcc_cv_as_mips_explicit = xno; then \
+    if test x$gcc_cv_as_mips_explicit_relocs = xno; then \
 
 $as_echo "#define MIPS_EXPLICIT_RELOCS MIPS_EXPLICIT_RELOCS_NONE" >>confdefs.h
 
diff --git a/gcc/configure.ac b/gcc/configure.ac
index 5cc9338bec4b..239856a4e202 100644
--- a/gcc/configure.ac
+++ b/gcc/configure.ac
@@ -5255,7 +5255,7 @@ LCF0:
 		 [Define if assembler supports %reloc.])])
     fi
 
-    if test x$gcc_cv_as_mips_explicit = xno; then \
+    if test x$gcc_cv_as_mips_explicit_relocs = xno; then \
       AC_DEFINE(MIPS_EXPLICIT_RELOCS, MIPS_EXPLICIT_RELOCS_NONE,
 		[Define if assembler supports %reloc.])
     fi

                 reply	other threads:[~2024-01-29 16:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240129163226.0DCC83858430@sourceware.org \
    --to=syq@gcc.gnu.org \
    --cc=gcc-cvs@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).