public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103383] Microblaze bswaphi2 can cause issues with delay slots Date: Thu, 02 Dec 2021 00:11:25 +0000 [thread overview] Message-ID: <bug-103383-4-VfA2NAAorj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103383-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103383 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Microblaze bswaphi2 |Microblaze bswaphi2 can | |cause issues with delay | |slots --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note I have no way to test the patch which I put here. I hope someone who understands Microblaze better and has a reasonable way to test it to take over this bug report. Also the maintainer of Microblaze seems not to be very active either ...
next prev parent reply other threads:[~2021-12-02 0:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-23 13:31 [Bug target/103383] New: Microblaze bswaphi2 rkujoth at motorolasolutions dot com 2021-11-23 15:03 ` [Bug target/103383] " rkujoth at motorolasolutions dot com 2021-11-24 3:14 ` pinskia at gcc dot gnu.org 2021-11-24 3:33 ` kujoth at gmail dot com 2021-11-24 3:37 ` pinskia at gcc dot gnu.org 2021-12-02 0:11 ` pinskia at gcc dot gnu.org [this message] 2021-12-02 3:00 ` [Bug target/103383] Microblaze bswaphi2 can cause issues with delay slots kujoth at gmail dot com 2021-12-02 15:43 ` eager at eagercon dot com 2021-12-03 14:08 ` rkujoth at motorolasolutions dot com 2021-12-03 15:07 ` rkujoth at motorolasolutions dot com
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-103383-4-VfA2NAAorj@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).