public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/99157] [ARM] libgcc -mcmse check always fail Date: Wed, 24 Feb 2021 16:03:16 +0000 [thread overview] Message-ID: <bug-99157-4-SRpkWCWc2w@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99157-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99157 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Christophe Lyon <clyon@gcc.gnu.org>: https://gcc.gnu.org/g:fcfd5cc0f428262fcce874a4c3b41e06d1296901 commit r10-9388-gfcfd5cc0f428262fcce874a4c3b41e06d1296901 Author: Christophe Lyon <christophe.lyon@linaro.org> Date: Wed Feb 24 15:51:52 2021 +0000 arm: Fix CMSE support detection in libgcc (PR target/99157) As discussed in the PR, the Makefile fragment lacks a double '$' to get the return-code from GCC invocation, resulting is CMSE support missing from multilibs. I checked that the simple patch proposed in the PR fixes the problem. 2021-02-23 Christophe Lyon <christophe.lyon@linaro.org> Hau Hsu <hsuhau617@gmail.com> PR target/99157 libgcc/ * config/arm/t-arm: Fix cmse support detection. (cherry picked from commit be30dd89926d5dd19d72f90c1586b0e2557fde43)
next prev parent reply other threads:[~2021-02-24 16:03 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-19 7:47 [Bug libgcc/99157] New: " hsuhau617 at gmail dot com 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 [this message] 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-SRpkWCWc2w@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: linkBe 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).