public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Johan Rydberg <jrydberg@rtmk.org>
Cc: cgen@sources.redhat.com
Subject: Re: adjusting cgen
Date: Wed, 12 Jun 2002 08:13:00 -0000	[thread overview]
Message-ID: <20020612111310.A24036@redhat.com> (raw)
In-Reply-To: <20020612041320.C16968@cockmaster.bredbandsbolaget.se>; from jrydberg@rtmk.org on Wed, Jun 12, 2002 at 04:13:20AM +0200

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

Hi -


> [...]
> 1)  Is it possible to adjust CGEN to recognize on-page branches?
>     This could be a huge optimization for me, since this will eliminate
>     the full tlb+mmu lookup for (near) branches.  

If nothing else, they could be detected within the branch instruction 
semantics.  They could set some private simulator state that signals
that the previously identified imem page is still valid.  Or even better,
this logic could be put into the general instruction execution loop
directly: if the new PC is on the same page as the old PC, then use
the previous value.


> 2)  Is it possible to adjust the -gen-argbuf-elm fn in sid-decode.scm to
>     generate bit fields instead of full integers?  [...]
>     What I would like to do is to reduce the size of the sem_fields union
>     to a total of 32-bits (for a 32-bit architecture).  [...]

Are you sure that this is a worthwhile thing to do?  You should mark
up the generated sources by hand once, and see if it makes a positive
or negative impact on performance.  If it's positive for interesting
hosts, we should do this cgen-wide.


> If you're intressted in the simulator, you can find information (ie
> the sources) at http://savannah.gnu.org/projects/guss/ .

Not to be discouraging, but can you explain why you'd like to build a
new simulator framework, when you're welcome to make contributions to
established ones like sid and even the older gdb simulators?  (It's of
course a good personal learning exercise to build things from scratch,
but please realize that there is a *lot* of work involved in making a
nice, fully featured framework.)


- FChE

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

  reply	other threads:[~2002-06-12 15:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-11 19:09 Johan Rydberg
2002-06-12  8:13 ` Frank Ch. Eigler [this message]
2002-06-16  8:04   ` Johan Rydberg

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=20020612111310.A24036@redhat.com \
    --to=fche@redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=jrydberg@rtmk.org \
    /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).