From: Yao Qi <yao@codesourcery.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 7/8] New port: TI C6x: test case fixes
Date: Tue, 09 Aug 2011 15:25:00 -0000 [thread overview]
Message-ID: <4E415152.8020905@codesourcery.com> (raw)
In-Reply-To: <201108091515.p79FFoUs007220@glazunov.sibelius.xs4all.nl>
On 08/09/2011 11:15 PM, Mark Kettenis wrote:
> Why depend on this NOMMU-magic? Just install the signal handler for
> bth SIGSEGV and SIGILL, try a store to (or perhaps a read from)
> address 0, and then fall through to executing an illegal instruction.
Because I want to reduce the scope of using invalid instruction. We
only need to know the invalid instruction for HAS_NOMMU arch, and emit
error if we forget to define an invalid instruction for a new NOMMU
port. Do it make sense?
--
Yao (é½å°§)
next prev parent reply other threads:[~2011-08-09 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 2:12 Yao Qi
2011-07-25 11:37 ` Yao Qi
2011-08-09 14:22 ` Pedro Alves
2011-08-09 15:03 ` Yao Qi
2011-08-09 15:17 ` Mark Kettenis
2011-08-09 15:25 ` Yao Qi [this message]
2011-08-10 12:28 ` Mark Kettenis
2011-08-10 14:05 ` Yao Qi
2011-08-14 16:24 ` Yao Qi
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=4E415152.8020905@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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