public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hsuhau617 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/99157] New: [ARM] libgcc -mcmse check always fail
Date: Fri, 19 Feb 2021 07:47:42 +0000 [thread overview]
Message-ID: <bug-99157-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99157
Bug ID: 99157
Summary: [ARM] libgcc -mcmse check always fail
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgcc
Assignee: unassigned at gcc dot gnu.org
Reporter: hsuhau617 at gmail dot com
Target Milestone: ---
When checking -mcmse support, it will always fail.
Because it checks the return value with "$?", but in makefile it should be
"$$?".
I have a simple patch for the bug:
--- a/libgcc/config/arm/t-arm
+++ b/libgcc/config/arm/t-arm
@@ -4,7 +4,7 @@ LIB1ASMFUNCS = _thumb1_case_sqi _thumb1_case_uqi
_thumb1_case_shi \
HAVE_CMSE:=$(findstring __ARM_FEATURE_CMSE,$(shell $(gcc_compile_bare) -dM -E
- </dev/null))
HAVE_V81M:=$(findstring armv8.1-m.main,$(gcc_compile_bare))
-ifeq ($(shell $(gcc_compile_bare) -E -mcmse - </dev/null >/dev/null
2>/dev/null; echo $?),0)
+ifeq ($(shell $(gcc_compile_bare) -E -mcmse - </dev/null >/dev/null
2>/dev/null; echo $$?),0)
CMSE_OPTS:=-mcmse
endif
next reply other threads:[~2021-02-19 7:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 7:47 hsuhau617 at gmail dot com [this message]
2021-02-19 9:46 ` [Bug libgcc/99157] " gcc-bugzilla at garstig dot org
2021-02-19 16:02 ` hsuhau617 at gmail dot com
2021-02-19 16:06 ` hsuhau617 at gmail dot com
2021-02-23 17:30 ` clyon at gcc dot gnu.org
2021-02-24 2:01 ` hsuhau617 at gmail dot com
2021-02-24 16:00 ` cvs-commit at gcc dot gnu.org
2021-02-24 16:03 ` cvs-commit at gcc dot gnu.org
2021-02-24 16:04 ` clyon at gcc dot gnu.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-99157-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).