public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/92999] [armhf] struct with adjacent __fp16's copies wrongly Date: Sat, 05 Nov 2022 07:42:19 +0000 [thread overview] Message-ID: <bug-92999-4-7SRG4t1b94@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-92999-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92999 Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |ramana at gcc dot gnu.org Ever confirmed|0 |1 Known to fail| |13.0 Last reconfirmed| |2022-11-05 --- Comment #2 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> --- confirmed on trunk. I think this is an issue in the way the registers are allocated for the VFP PCS.
next parent reply other threads:[~2022-11-05 7:42 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-92999-4@http.gcc.gnu.org/bugzilla/> 2022-11-05 7:42 ` ramana at gcc dot gnu.org [this message] 2022-11-08 6:37 ` ramana 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-92999-4-7SRG4t1b94@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).