public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104144] [12 Regression] build fails due to: Error: unknown architecture `armv9-a' Date: Tue, 12 Apr 2022 09:46:42 +0000 [thread overview] Message-ID: <bug-104144-4-KSj64qXF2w@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104144-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104144 Richard Earnshaw <rearnsha at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #10 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- Fixed, by adjusting the selection of multilibs that are needed. There's no benefit to building armv9-a multilibs, so use those built for armv8-a.
prev parent reply other threads:[~2022-04-12 9:46 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-20 12:26 [Bug web/104144] New: [12 Regression] --enable-version-specific-runtime-libs " marxin at gcc dot gnu.org 2022-01-20 12:26 ` [Bug web/104144] " marxin at gcc dot gnu.org 2022-01-20 12:31 ` [Bug target/104144] " rguenth at gcc dot gnu.org 2022-01-20 12:35 ` clyon at gcc dot gnu.org 2022-01-20 12:48 ` [Bug target/104144] [12 Regression] build " rguenth at gcc dot gnu.org 2022-01-20 13:38 ` rearnsha at gcc dot gnu.org 2022-01-20 14:10 ` rguenth at gcc dot gnu.org 2022-01-20 14:12 ` wirkus at gcc dot gnu.org 2022-02-25 13:06 ` marxin at gcc dot gnu.org 2022-02-25 14:58 ` przemyslaw.wirkus at arm dot com 2022-04-12 9:41 ` cvs-commit at gcc dot gnu.org 2022-04-12 9:46 ` rearnsha at gcc dot gnu.org [this message]
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-104144-4-KSj64qXF2w@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).