From: Joseph A <joseph.altmaier@gmail.com>
To: cgen@sourceware.org
Subject: Re: how can one achieve pipelined operation?
Date: Thu, 30 Jul 2009 20:12:00 -0000 [thread overview]
Message-ID: <24746519.post@talk.nabble.com> (raw)
In-Reply-To: <20090712022717.GB2347@redhat.com>
> I get two errors which say "error: invalid initialization of
> reference of type '%ISA1%::write_stacks&' from expression of type
> '%CPU%::write_stacks'" and "error: invalid initialization of
> reference of type '%ISA2%::write_stacks&' from expression of type
> '%CPU%::write_stacks'".
Problem solved. These two errors were caused by an incorrect makefile as
well as incorrect code. In my %CPU%.h file I had declared write_stacks as
%CPU%::write_stacks write_stacks. Instead I needed to declare two separate
stacks, %ISA1%::write_stacks write_stacks1 and %ISA2%::write_stacks
write_stacks2. I also discovered that I had not told CGEN to generate the
files %CPU%-%ISAX%-defs.h. This caused me to get an incomplete definition
error when I tried to make the altered code. I fixed this by going into the
makefile in src/sid/component/cgen-cpu/%CPU% and altering it such that it
would cause CGEN to generate the defs files, using the sh and mt ports as
examples.
--
View this message in context: http://www.nabble.com/how-can-one-achieve-pipelined-operation--tp24210860p24746519.html
Sent from the Sourceware - cgen list mailing list archive at Nabble.com.
next prev parent reply other threads:[~2009-07-30 20:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 20:54 Joseph A
2009-07-01 10:50 ` Frank Ch. Eigler
2009-07-02 3:05 ` Doug Evans
2009-07-02 12:09 ` Dave Korn
2009-07-02 12:29 ` Frank Ch. Eigler
2009-07-02 16:45 ` Joseph A
2009-07-12 2:27 ` Frank Ch. Eigler
2009-07-30 20:12 ` Joseph A [this message]
2009-07-30 20:19 ` Frank Ch. Eigler
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=24746519.post@talk.nabble.com \
--to=joseph.altmaier@gmail.com \
--cc=cgen@sourceware.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).