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/95420] arm-wrs-vxworks7: xgcc: error: unrecognised -mcpu target: armv7-a Date: Tue, 02 Jun 2020 08:37:36 +0000 [thread overview] Message-ID: <bug-95420-4-yh1YvQ1ab3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95420-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95420 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Iain Buclaw <ibuclaw@gcc.gnu.org>: https://gcc.gnu.org/g:86b14bb1a93d8ef01678d132013a2006a4f00deb commit r11-786-g86b14bb1a93d8ef01678d132013a2006a4f00deb Author: Iain Buclaw <ibuclaw@gdcproject.org> Date: Mon Jun 1 00:18:44 2020 +0200 Fix unrecognised -mcpu target 'armv7-a' on arm-wrs-vxworks7 In the removal of arm-wrs-vxworks, the default cpu was updated from arm8 to armv7-a, but this is not recognized as a valid -mcpu target. There is however generic-armv7-a, which was likely the intended cpu that should have been used instead. gcc/ChangeLog: PR target/95420 * config.gcc (arm-wrs-vxworks7*): Set default cpu to generic-armv7-a.
next prev parent reply other threads:[~2020-06-02 8:37 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-29 15:31 [Bug target/95420] New: " ibuclaw at gdcproject dot org 2020-05-31 5:36 ` [Bug target/95420] " ibuclaw at gdcproject dot org 2020-05-31 20:07 ` ibuclaw at gdcproject dot org 2020-06-02 8:37 ` cvs-commit at gcc dot gnu.org [this message] 2020-06-02 8:38 ` cvs-commit at gcc dot gnu.org 2020-07-02 23:21 ` ibuclaw at gdcproject 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-95420-4-yh1YvQ1ab3@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).