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/106279] reload problem on arm iwmmxt Date: Thu, 01 Sep 2022 13:01:44 +0000 [thread overview] Message-ID: <bug-106279-4-JbEYLd6Mqe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106279-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106279 Richard Earnshaw <rearnsha at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-09-01 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #4 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- In a general cross compiler you need: -march=iwmmxt -mfpu=vfp -mfloat-abi=hard to reproduce. This seems to need a combination of VFP, iWMMX and the hard-float ABI. I don't think we've ever claimed to support this. Whilst there may be a few devices with both iWMMX and VFP present, I think that's mostly for backwards compatibility. So I think we should resolve this as WONTFIX, but it would be nice if the compiler could reject this upfront rather than ICEing later on.
next prev parent reply other threads:[~2022-09-01 13:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-13 8:01 [Bug target/106279] New: " dcb314 at hotmail dot com 2022-07-13 9:10 ` [Bug target/106279] " wilco at gcc dot gnu.org 2022-07-13 9:15 ` dcb314 at hotmail dot com 2022-07-13 9:17 ` wilco at gcc dot gnu.org 2022-09-01 13:01 ` rearnsha at gcc dot gnu.org [this message] 2022-09-01 13:06 ` rearnsha 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-106279-4-JbEYLd6Mqe@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).