public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] x86_64: State assembler is being tested on sysdeps/x86/configure
Date: Tue,  6 Dec 2022 16:48:28 +0000 (GMT)	[thread overview]
Message-ID: <20221206164828.D923738469BC@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=8d6083717c1df492d1276b302180df0dcdddb4cf

commit 8d6083717c1df492d1276b302180df0dcdddb4cf
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Tue Dec 6 13:47:47 2022 -0300

    x86_64: State assembler is being tested on sysdeps/x86/configure

Diff:
---
 sysdeps/x86/configure    | 4 ++--
 sysdeps/x86/configure.ac | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/sysdeps/x86/configure b/sysdeps/x86/configure
index f80fedd9dd..6135b17652 100644
--- a/sysdeps/x86/configure
+++ b/sysdeps/x86/configure
@@ -33,8 +33,8 @@ $as_echo "$libc_cv_x86_cet_available" >&6; }
 fi
 if test $enable_cet != no; then
   # Check if assembler supports CET.
-  { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether compiler supports CET" >&5
-$as_echo_n "checking whether compiler supports CET... " >&6; }
+  { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether assembler supports CET" >&5
+$as_echo_n "checking whether assembler supports CET... " >&6; }
 if ${libc_cv_x86_cet_as+:} false; then :
   $as_echo_n "(cached) " >&6
 else
diff --git a/sysdeps/x86/configure.ac b/sysdeps/x86/configure.ac
index ac55dc674a..c854bc74ca 100644
--- a/sysdeps/x86/configure.ac
+++ b/sysdeps/x86/configure.ac
@@ -22,7 +22,7 @@ EOF
 fi
 if test $enable_cet != no; then
   # Check if assembler supports CET.
-  AC_CACHE_CHECK(whether compiler supports CET,
+  AC_CACHE_CHECK(whether assembler supports CET,
 		 libc_cv_x86_cet_as, [dnl
 cat > conftest.s <<EOF
 	incsspd %ecx

                 reply	other threads:[~2022-12-06 16:48 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=20221206164828.D923738469BC@sourceware.org \
    --to=azanella@sourceware.org \
    --cc=glibc-cvs@sourceware.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).