public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Felix.Riemann at sma dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/29698] New: Configuring for AArch32 on ARMv8+ disables optimizations
Date: Tue, 18 Oct 2022 15:13:56 +0000 [thread overview]
Message-ID: <bug-29698-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29698
Bug ID: 29698
Summary: Configuring for AArch32 on ARMv8+ disables
optimizations
Product: glibc
Version: 2.37
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: Felix.Riemann at sma dot de
CC: carlos at redhat dot com
Target Milestone: ---
Configuring glibc for ARM AArch32 with a compiler that optimizes for ARMv8
causes configure to misdetect the target and disable all optimizations/fall
back on ARMv5:
$ CFLAGS="-O2 -march=armv8-a" ../configure --prefix=/usr
--host=arm-linux-gnueabi
configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu
checking build system type... x86_64-pc-linux-gnu
checking host system type... arm-unknown-linux-gnueabi
checking for arm-linux-gnueabi-gcc... arm-linux-gnueabi-gcc
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether arm-linux-gnueabi-gcc accepts -g... yes
checking for gcc... gcc
checking for arm-linux-gnueabi-readelf... arm-linux-gnueabi-readelf
checking for arm-linux-gnueabi-g++... arm-linux-gnueabi-g++
checking whether we are using the GNU C++ compiler... yes
checking whether arm-linux-gnueabi-g++ accepts -g... yes
checking whether arm-linux-gnueabi-g++ can link programs... yes
checking for sysdeps preconfigure fragments... aarch64 alpha arc arm configure:
WARNING: arm/preconfigure: Did not find ARM architecture type; using default
This is due to the glob in sysdeps/arm/preconfigure.ac being underquoted so
that m4 will remove the brackets for ARMv8/v9. I'll send a patch shortly.
I picked 2.37 as it is reproducable on git master but I could reproduce it in
versions going back to at least 2.28.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-10-18 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 15:13 Felix.Riemann at sma dot de [this message]
2022-10-18 15:46 ` [Bug build/29698] " Felix.Riemann at sma dot de
2022-10-20 14:38 ` adhemerval.zanella at linaro dot 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-29698-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).