public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55295] [SH] Add support for fipr instruction
Date: Tue, 21 Mar 2023 11:52:57 +0000 [thread overview]
Message-ID: <bug-55295-4-e0XgRRIVk0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55295-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55295
--- Comment #17 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to Luke Benstead from comment #16)
> OK so perhaps adding __builtin_sh_fipr is a good first step?
Yeah, you can try and see if it produces any useful results for you.
prev parent reply other threads:[~2023-03-21 11:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 22:29 [Bug target/55295] New: " olegendo at gcc dot gnu.org
2012-11-12 22:39 ` [Bug target/55295] " olegendo at gcc dot gnu.org
2013-03-04 16:24 ` turkeyman at gmail dot com
2013-03-04 21:51 ` olegendo at gcc dot gnu.org
2013-03-05 1:55 ` turkeyman at gmail dot com
2013-03-05 12:28 ` olegendo at gcc dot gnu.org
2013-03-05 12:53 ` turkeyman at gmail dot com
2013-03-06 1:05 ` olegendo at gcc dot gnu.org
2013-03-13 18:21 ` olegendo at gcc dot gnu.org
2014-12-07 23:49 ` olegendo at gcc dot gnu.org
2014-12-09 22:37 ` olegendo at gcc dot gnu.org
2015-03-01 19:06 ` olegendo at gcc dot gnu.org
2015-03-02 0:17 ` turkeyman at gmail dot com
2015-03-02 9:00 ` olegendo at gcc dot gnu.org
2023-03-21 9:38 ` kazade at gmail dot com
2023-03-21 9:43 ` olegendo at gcc dot gnu.org
2023-03-21 11:46 ` kazade at gmail dot com
2023-03-21 11:52 ` olegendo 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-55295-4-e0XgRRIVk0@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: link
Be 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).