public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/54760] [SH] Add __builtin_thread_pointer, __builtin_set_thread_pointer
Date: Fri, 12 Oct 2012 00:14:00 -0000 [thread overview]
Message-ID: <bug-54760-4-OIRbY15oSK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54760-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54760
--- Comment #6 from Kazumoto Kojima <kkojima at gcc dot gnu.org> 2012-10-12 00:13:51 UTC ---
(In reply to comment #5)
> Kaz, do you happen to know something regarding this matter?
My SH4 software manual says for STC that all stc/stc.l instructions
except stc gbr,rn/stc gbr,@-rn are privileged instructions which
might cause an illegal exception in user mode. LDC has a similar
remark.
next prev parent reply other threads:[~2012-10-12 0:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 17:00 [Bug target/54760] New: " olegendo at gcc dot gnu.org
2012-09-30 17:01 ` [Bug target/54760] " olegendo at gcc dot gnu.org
2012-10-06 11:20 ` olegendo at gcc dot gnu.org
2012-10-08 2:01 ` olegendo at gcc dot gnu.org
2012-10-09 18:59 ` olegendo at gcc dot gnu.org
2012-10-09 19:42 ` olegendo at gcc dot gnu.org
2012-10-11 20:29 ` olegendo at gcc dot gnu.org
2012-10-12 0:14 ` kkojima at gcc dot gnu.org [this message]
2012-10-12 0:27 ` olegendo at gcc dot gnu.org
2012-10-12 0:43 ` kkojima at gcc dot gnu.org
2012-10-12 0:46 ` olegendo at gcc dot gnu.org
2012-10-12 0:51 ` olegendo at gcc dot gnu.org
2012-10-15 22:05 ` olegendo at gcc dot gnu.org
2012-10-23 19:25 ` amylaar at gcc dot gnu.org
2012-10-27 13:41 ` olegendo at gcc dot gnu.org
2013-03-09 12:36 ` olegendo 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-54760-4-OIRbY15oSK@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).