From: wkt@tuhs.org (Warren Toomey)
Subject: [Unix-jun72] last1120 C compiler added to svn
Date: Mon, 5 May 2008 14:52:29 +1000 [thread overview]
Message-ID: <20080505045229.GA76763@minnie.tuhs.org> (raw)
I'm still working on the last1120 C compiler, so I've added the original code
to svn. Right now, the compiler executes fine under Apout (enough to recompile
itself), but not on V1 with the 0407 patch. I can compile simple C programs,
and execute the resulting 0407 binary on V1. I'm running this program to get a
memory dump of the process while it is running:
main()
{
char c[];
int i;
printf("Hello world\n");
c= main;
while (c != 0) {
i= *c & 0277;
printf("%o %o\n", c, i);
c++;
}
}
so I can compare the Apout memory environment with the V1 memory environment.
But it's very sloooow. I wonder why; V7 on simh is much faster than V1.
Cheers,
Warren
P.S The C compiler doesn't have for loops :-)
next reply other threads:[~2008-05-05 4:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 4:52 Warren Toomey [this message]
2008-05-05 9:10 ` Peter Jeremy
2008-05-05 11:36 ` [Unix-jun72] Why is V1 so slow? Warren Toomey
2008-05-05 11:44 ` Warren Toomey
2008-05-07 10:19 ` P.A.Osborne
2008-05-07 11:14 ` Warren Toomey
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=20080505045229.GA76763@minnie.tuhs.org \
--to=wkt@tuhs.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 NNTP newsgroup(s).