public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Meissner <meissner@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/meissner/heads/dmf004)] Fix typo.
Date: Thu, 17 Nov 2022 21:54:09 +0000 (GMT)	[thread overview]
Message-ID: <20221117215409.D3F87384F6DC@sourceware.org> (raw)

https://gcc.gnu.org/g:c3537650f8d2ad958db933530002b5b0ba97e360

commit c3537650f8d2ad958db933530002b5b0ba97e360
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Fri Nov 11 23:41:43 2022 -0500

    Fix typo.
    
    2022-11-11   Michael Meissner  <meissner@linux.ibm.com>
    
    gcc/testsuite/
    
            * lib/target-supports.exp (check_effective_target_powerpc_future_ok):
            Fix typo.

Diff:
---
 gcc/testsuite/lib/target-supports.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
index ca33a658f7e..56a12b45aeb 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -6555,7 +6555,7 @@ proc check_effective_target_powerpc_dense_math_ok { } {
 
 # Return 1 if this is a PowerPC target supporting -mcpu=future which enables
 # the saturating subtract instruction.
-proc check_effective_target_powerpc_subfus_ok { } {
+proc check_effective_target_powerpc_future_ok { } {
 	return [check_no_compiler_messages powerpc_future_ok object {
 	    #ifndef _ARCH_PWR_FUTURE
 	    #error "not -mcpu=future"

             reply	other threads:[~2022-11-17 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 21:54 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-12  4:42 Michael Meissner

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=20221117215409.D3F87384F6DC@sourceware.org \
    --to=meissner@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).