From: Mark Mitchell <mark@codesourcery.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Mike Stump <mikestump@comcast.net>,
gcc-patches@gcc.gnu.org, rearnshaw@arm.com,
paul@codesourcery.com
Subject: Re: RFA: ARM: Implement __builtin_trap
Date: Thu, 09 Sep 2010 18:46:00 -0000 [thread overview]
Message-ID: <4C892748.4030600@codesourcery.com> (raw)
In-Reply-To: <4C892557.6070908@caviumnetworks.com>
On 9/9/2010 11:20 AM, David Daney wrote:
> I saw that, and I have no objections to that patch. But I was thinking
> that this essentially augments the ABI. Could or should this be
> coordinated with the maintainers of any ARM ABIs?
Do other psABIs document how __builtin_trap is implemented?
Richard E. is certainly in a position to comment on this. The only
issue I see is that we're "using up" an instruction in the undefined
instruction space, meaning that it can't be used in some other magic way
by an OS. Linux presently uses an undefined instruction as a software
breakpoint. (I'm not sure why it does that instead of using an SVC
instruction?) But is there other stuff out there that might need this?
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
next prev parent reply other threads:[~2010-09-09 18:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 6:10 Mark Mitchell
2010-09-08 23:05 ` Mike Stump
2010-09-08 23:18 ` Mark Mitchell
2010-09-09 18:34 ` David Daney
2010-09-09 18:46 ` Mark Mitchell [this message]
2010-09-09 18:49 ` Chris Lattner
2010-09-09 19:23 ` Mark Mitchell
2010-09-09 21:59 ` Chris Lattner
2010-09-09 22:27 ` Anton Korobeynikov
2010-09-10 10:13 ` Richard Earnshaw
2010-09-10 13:12 ` Mikael Pettersson
2010-09-10 14:34 ` Mark Mitchell
2010-09-28 18:07 ` Mark Mitchell
2010-09-09 19:30 ` Daniel Jacobowitz
2010-09-09 21:25 ` Mark Mitchell
2010-09-09 21:49 ` Daniel Jacobowitz
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=4C892748.4030600@codesourcery.com \
--to=mark@codesourcery.com \
--cc=ddaney@caviumnetworks.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=paul@codesourcery.com \
--cc=rearnshaw@arm.com \
/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).