From: Alan Lehotsky <apl@alum.mit.edu>
To: cgen@sources.redhat.com
Subject: Simulating different models using a single simulator...
Date: Sat, 20 Oct 2001 09:26:00 -0000 [thread overview]
Message-ID: <p04330103b81f14502210@[192.168.1.254]> (raw)
It appears that the
--model <name>
flag to the simulator allows one to indicate WHICH model of a cpu family is to be simulated.
What I'm wondering about is HOW to test the model selected within the (define-insn ...)?
What I'd like to do is conditionally test the model and execute slightly different code paths in
the simulator. [There are only 6 instructions out of about 40 that are different between the two
models....
-- Al
--
------------------------------------------------------------------------
Quality Software Management
http://home.earthlink.net/~qsmgmt
apl@alum.mit.edu
(978)287-0435 Voice
(978)808-6836 Cell
(978)287-0436 Fax
Software Process Improvement and Management Consulting
Language Design and Compiler Implementation
WARNING: multiple messages have this Message-ID
From: Alan Lehotsky <apl@alum.mit.edu>
To: cgen@sources.redhat.com
Subject: Simulating different models using a single simulator...
Date: Mon, 19 Nov 2001 12:16:00 -0000 [thread overview]
Message-ID: <p04330103b81f14502210@[192.168.1.254]> (raw)
Message-ID: <20011119121600.1mSeo-9W5PwRN6xeOAChY394qaefjF4Cl6SrINMyOPU@z> (raw)
It appears that the
--model <name>
flag to the simulator allows one to indicate WHICH model of a cpu family is to be simulated.
What I'm wondering about is HOW to test the model selected within the (define-insn ...)?
What I'd like to do is conditionally test the model and execute slightly different code paths in
the simulator. [There are only 6 instructions out of about 40 that are different between the two
models....
-- Al
--
------------------------------------------------------------------------
Quality Software Management
http://home.earthlink.net/~qsmgmt
apl@alum.mit.edu
(978)287-0435 Voice
(978)808-6836 Cell
(978)287-0436 Fax
Software Process Improvement and Management Consulting
Language Design and Compiler Implementation
next reply other threads:[~2001-11-19 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-20 9:26 Alan Lehotsky [this message]
2001-11-07 7:13 ` Frank Ch. Eigler
2001-11-23 8:07 ` Frank Ch. Eigler
2001-11-19 12:16 ` Alan Lehotsky
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='p04330103b81f14502210@[192.168.1.254]' \
--to=apl@alum.mit.edu \
--cc=cgen@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).