Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: <duane@duaneellis.com>
To: "Mike Frysinger" <vapier@gentoo.org>,
	 "ISHIKAWA, chiaki" <ishikawa@yk.rim.or.jp>
Cc: gdb@sourceware.org, ysato@users.sourceforge.jp
Subject: RE: h8300 sim: what is "eightbit" memory ?
Date: Wed, 17 Aug 2016 18:35:00 -0000	[thread overview]
Message-ID: <20160817113508.5c1bb9f86d671edec44bb378f25c04cc.5ecda5525d.wbe@email03.godaddy.com> (raw)

mike>> if eightbit is just an address mode, that's dirt simple to handle
mike>> a (void *)0 will go to the same memory location regardless of the

mike>> addr mode used by an insn. but it isn't what the sim is doing
today :(.

If I remember correctly, the arm simulator does various calculations and
pipeline tracking.
It's been a while, but it was doing this in the giant instruction switch
statement.

I've not read or looked at the H8 simulator does the H8 simulator sort
of "count instruction/clock time" - based on memory accesses?

The old 6502 had a very similar zero page feature (first 256 bytes) -
aka: a zero page instructions.

Accessing zero page using a zero page instruction required 3 clocks
(aka: the first 256 bytes)
Accessing absolute required 4 clocks, but you *CAN* access zero page in
absolute mode if you choose
This was useful when I wrote bit-bang uart simulation code (ie: Tight SW
loop - to emulate a uart via GPIO pin)

Thus - from a logical view the "memory is just memory" end of story.

if this is not evident in the simulation code, this might have been a
planned feature that never materialized or was never finished.

this wiki page talks about it:

https://en.wikipedia.org/wiki/Zero_page




         reply	other threads:[~2016-08-17 18:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17  2:27 Mike Frysinger
2016-08-17  5:18 ` ISHIKAWA,chiaki
2016-08-17 18:07   ` Mike Frysinger
2016-08-17 18:35     ` duane [this message]
2016-08-17 18:53       ` Mike Frysinger

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=20160817113508.5c1bb9f86d671edec44bb378f25c04cc.5ecda5525d.wbe@email03.godaddy.com \
    --to=duane@duaneellis.com \
    --cc=gdb@sourceware.org \
    --cc=ishikawa@yk.rim.or.jp \
    --cc=vapier@gentoo.org \
    --cc=ysato@users.sourceforge.jp \
    /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