From: "Frank Ch. Eigler" <fche@redhat.com>
To: Pavel Baranov <pavel.baranov@ubicom.com>
Cc: cgen@sources.redhat.com
Subject: Re: Changed .cpu -> nothing happens
Date: Thu, 26 Apr 2001 17:04:00 -0000 [thread overview]
Message-ID: <20010426200413.B30652@redhat.com> (raw)
In-Reply-To: <470AE13EFEA7D31197C000508B139C67E40667@fenway.scenix.com>
Hi -
On Thu, Apr 26, 2001 at 02:33:26PM -0700, Pavel Baranov wrote:
: I changed the 'done' field from 1 -> 2 in .cpu file
: (in define model...unit...) [...]
: Previously I also tried to add new units to model description in
: .cpu file and nothing happened.
: Why nothing was changed? Where is the problem?
This is because the functional unit latency modelling code needs
special options for cgen to even look at; the model/unit is now
being summarily ignored for this port. Look at sim/fr30 for a
better idea what's involved.
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE66Ld9VZbdDOm/ZT0RAqzgAJ95WgRE0QqzL7G2y6cBVhRUcUDlegCeJUcG
F7K7c/GGzkZJKaGuLTP0LCI=
=p76x
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2001-04-26 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 14:34 Pavel Baranov
2001-04-26 17:04 ` Frank Ch. Eigler [this message]
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=20010426200413.B30652@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=pavel.baranov@ubicom.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).