Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: nick clifton <nickc@redhat.com>
Cc: dj@redhat.com, gdb-patches@sourceware.org
Subject: Re: RFA: V850 sim: various fixes.
Date: Mon, 10 Sep 2012 16:56:00 -0000	[thread overview]
Message-ID: <CAJaTeTrO2t3+d7rxeTKK9W_eCaB-ZsZDU9G8BdBi6k-vyA_Y=w@mail.gmail.com> (raw)
In-Reply-To: <504E0877.2040202@redhat.com>

On Mon, Sep 10, 2012 at 8:34 AM, nick clifton wrote:
>>>    It also adds a snippet of code to catch attempts to
>>>    execute code via a NULL pointer.
>>
>> usually the simulator represents the hardware.  so if the hardware has
>> memory at address 0 and someone were to load up an image with code
>> there, there's nothing invalid when it comes to jumping there.
>
> Personally I see the simulator as more of a testing and debugging tool.  It
> does not try to be hardware accurate - it does not model the cache for
> example - so adding a feature that helps catch program errors, even if it
> not strictly modelling the hardware, seems OK to me.

well, you're talking about cycle accurate simulators vs functional
accurate simulators.  yes, many sims don't model down to the cache
level (although that functionality is available), nor things like the
pipeline, but at a functional level, those don't matter.  being able
to read/write/execute address 0 is a functional aspect.

i'm not against adding a flag to control this, but in general i don't
think completely blocking a functional aspect is correct ... although
DJ is the v850 guy, and i certainly won't force this policy on every
sim since not everyone uses the sim as a generically as i do.
-mike


  reply	other threads:[~2012-09-10 16:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 10:21 Nick Clifton
2012-09-10 15:27 ` Mike Frysinger
2012-09-10 15:41   ` nick clifton
2012-09-10 16:56     ` Mike Frysinger [this message]
2012-09-10 15:50   ` DJ Delorie
2012-09-10 16:33     ` nick clifton
2012-09-13  1:13       ` DJ Delorie

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='CAJaTeTrO2t3+d7rxeTKK9W_eCaB-ZsZDU9G8BdBi6k-vyA_Y=w@mail.gmail.com' \
    --to=vapier@gentoo.org \
    --cc=dj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@redhat.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