public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "benh at kernel dot crashing.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/29394] New: Possible typo in sysdeps/aarch64/configure{.ac}
Date: Fri, 22 Jul 2022 04:10:42 +0000	[thread overview]
Message-ID: <bug-29394-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29394

            Bug ID: 29394
           Summary: Possible typo in sysdeps/aarch64/configure{.ac}
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: benh at kernel dot crashing.org
                CC: carlos at redhat dot com
  Target Milestone: ---

So I'm not super familiar with those configure macros, but I noticed this in
configure.ac"

# Check if asm support armv8.2-a+sve
AC_CACHE_CHECK(for SVE support in assembler, libc_cv_asm_sve, [dnl
cat > conftest.s <<\EOF
        ptrue p0.b
EOF
if AC_TRY_COMMAND(${CC-cc} -c -march=armv8.2-a+sve conftest.s
1>&AS_MESSAGE_LOG_FD); then
  libc_cv_aarch64_sve_asm=yes
else
  libc_cv_aarch64_sve_asm=no
fi
rm -f conftest*])
if test $libc_cv_aarch64_sve_asm = yes; then
  AC_DEFINE(HAVE_AARCH64_SVE_ASM)
fi

Note the use of "libc_cv_asm_sve" vs. "libc_cv_aarch64_sve_asm"

This doesn't match other tests in the same file and might explain why the
result isn't displayed properly when running configure...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-07-22  4:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22  4:10 benh at kernel dot crashing.org [this message]
2022-08-11 16:19 ` [Bug build/29394] " wdijkstr at arm dot com
2023-02-28 15:52 ` schwab@linux-m68k.org

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=bug-29394-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).