From: "\"Nils O. Selåsdal\"" <noselasd@asgaard.homelinux.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 8c dying with out of fixed registers
Date: Fri, 6 May 2005 22:34:29 +0200 [thread overview]
Message-ID: <427BD4D5.4070302@asgaard.homelinux.org> (raw)
In-Reply-To: <85082ec2f1cbf83a5db6ecf7ff111f3b@plan9.ucalgary.ca>
andrey mirtchovski wrote:
> 8c has a 32K char limit for each line of code it processes. i had a
> copy somewhere with that limit increased to 128K, but that's just a
> partial solution.
That isn't the problem here though, as far as I can see.
The snippet I mailed is a total of 569 bytes :-)
( the original code was also way below 32K.)
next parent reply other threads:[~2005-05-06 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <85082ec2f1cbf83a5db6ecf7ff111f3b@plan9.ucalgary.ca>
2005-05-06 20:34 ` "Nils O. Selåsdal" [this message]
2005-05-06 21:00 ` andrey mirtchovski
2005-05-06 21:08 ` andrey mirtchovski
[not found] <a27dc8e08d6f5936960797156b50a514@plan9.ucalgary.ca>
2005-05-06 21:17 ` "Nils O. Selåsdal"
2005-05-06 19:59 "Nils O. Selåsdal"
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=427BD4D5.4070302@asgaard.homelinux.org \
--to=noselasd@asgaard.homelinux.org \
--cc=9fans@cse.psu.edu \
/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).