Memory accesses

public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed

* Memory accesses
@ 2003-01-29 19:21 Jose Luis Ayala
  2003-01-29 19:39 ` Frank Ch. Eigler
  0 siblings, 1 reply; 2+ messages in thread
From: Jose Luis Ayala @ 2003-01-29 19:21 UTC (permalink / raw)
  To: cgen

Hi!

I'm writing some simple code to trace memory accesses while the
simulator runs. As I want this works for different targets, I need to
put the code into the common simulator sources. I've selected the
sim-utils.c file (sim/common/sim-utils.c), where a 'case' structure
seems to take care of that (access_read, access_write, access_exec...). 

Does it look ok? or could you suggest me any more proper place/way for
that?

Thanks a lot!

Jose

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Memory accesses
  2003-01-29 19:21 Memory accesses Jose Luis Ayala
@ 2003-01-29 19:39 ` Frank Ch. Eigler
  0 siblings, 0 replies; 2+ messages in thread
From: Frank Ch. Eigler @ 2003-01-29 19:39 UTC (permalink / raw)
  To: Jose Luis Ayala; +Cc: cgen

[-- Attachment #1: Type: text/plain, Size: 469 bytes --]

Hi -

On Wed, Jan 29, 2003 at 08:22:39PM +0100, Jose Luis Ayala wrote:
> I'm writing some simple code to trace memory accesses while the
> simulator runs. As I want this works for different targets, I need to
> put the code into the common simulator sources. [...]

This is not really a CGEN issue.  If you want to deal with either
the gdb simulators or with sid, then chances are the command line
option "--trace-core" will produce tracing output you can use.

- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-01-29 19:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-01-29 19:21 Memory accesses Jose Luis Ayala
2003-01-29 19:39 ` Frank Ch. Eigler

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).