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 target/93053] [9 Regression] libgcc build failure with old binutils on aarch64
Date: Wed, 22 Apr 2020 16:10:01 +0000 [thread overview]
Message-ID: <bug-93053-4-bP3B7ySkuE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93053-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93053
--- Comment #16 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Andre Simoes Dias Vieira
<avieira@gcc.gnu.org>:
https://gcc.gnu.org/g:a69a60c4969cea06c1d44b5e3e4970595041e510
commit r8-10213-ga69a60c4969cea06c1d44b5e3e4970595041e510
Author: Andre Vieira <andre.simoesdiasvieira@arm.com>
Date: Thu Apr 16 10:16:18 2020 +0100
aarch64: Fix bootstrap with old binutils [PR93053]
As reported in the PR, GCC 10 (and also 9.3.1 but not 9.3.0) fails to build
when using older binutils which lack LSE support, because those
instructions
are used in libgcc.
Thanks to Kyrylo's hint, the following patches (hopefully) allow it to
build
even with older binutils by using .inst directive if LSE support isn't
available in the assembler.
2020-04-16 Andre Vieira <andre.simoesdiasvieira@arm.com>
Backport from mainline
2020-04-15 Jakub Jelinek <jakub@redhat.com>
PR target/93053
* configure.ac (LIBGCC_CHECK_AS_LSE): Add HAVE_AS_LSE checking.
* config/aarch64/lse.S: Include auto-target.h, if HAVE_AS_LSE
is not defined, use just .arch armv8-a.
(B, M, N, OPN): Define.
(COMMENT): New .macro.
(CAS, CASP, SWP, LDOP): Use .inst directive if HAVE_AS_LSE is not
defined. Otherwise, move the operands right after the glue? and
comment out operands where the macros are used.
* configure: Regenerated.
* config.in: Regenerated.
next prev parent reply other threads:[~2020-04-22 16:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-93053-4@http.gcc.gnu.org/bugzilla/>
2020-03-20 11:43 ` [Bug target/93053] [10 " rguenth at gcc dot gnu.org
2020-04-14 10:38 ` jakub at gcc dot gnu.org
2020-04-14 10:41 ` ktkachov at gcc dot gnu.org
2020-04-14 11:59 ` jakub at gcc dot gnu.org
2020-04-14 12:51 ` [Bug target/93053] [9/10 " jakub at gcc dot gnu.org
2020-04-14 14:36 ` rguenth at gcc dot gnu.org
2020-04-15 9:02 ` cvs-commit at gcc dot gnu.org
2020-04-15 9:14 ` [Bug target/93053] [9 " jakub at gcc dot gnu.org
2020-04-22 14:18 ` cvs-commit at gcc dot gnu.org
2020-04-22 16:10 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-22 16:31 ` avieira 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-93053-4-bP3B7ySkuE@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).