From: Russ Cox <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ports update
Date: Fri, 26 Mar 2004 14:16:23 -0500 [thread overview]
Message-ID: <40648187.6050901@swtch.com> (raw)
In-Reply-To: <200403261905.i2QJ5OA19487@plg2.math.uwaterloo.ca>
Richard C Bilson wrote:
>>I'm running quite reliably under Linux/x86 for all day-to-day work,
>>
>>
>
>Actually, I just blew away my existing copy and did a fresh check-out,
>and now things seem to work on Linux. Thanks, cvs.
>
>I'll see if I can get purify to work on SunOS.
>
>
I did just fix an important bug in the resize code
that could cause stray memory accesses after you've
resized the window. And I rolled in Axel's new startup
code changes -- they handle the case where you're
sitting at a (say) 24-bit display but have your default
window depth set to 8-bit.
William Josephson suggests that the setlabel/gotolabel
implementation for SPARC may not be handling register
window overflow/underflow properly. We have a different
implementation in tra (and of course I don't know the history
of either one) that might be worth trying, but I've done
my time fighting this stuff for the day. ("SPARC" is "CRAPS"
backwards. -- rob)
Russ
next prev parent reply other threads:[~2004-03-26 19:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 19:05 Richard C Bilson
2004-03-26 19:16 ` Russ Cox [this message]
2004-03-26 19:27 ` Axel Belinfante
2004-03-27 13:10 ` boyd, rounin
2004-03-27 13:09 ` boyd, rounin
-- strict thread matches above, loose matches on Subject: below --
2004-03-26 15:52 Richard C Bilson
2004-03-26 16:07 ` Axel Belinfante
2004-03-26 16:21 ` Russ Cox
2004-03-26 16:26 ` Sam
2004-03-26 2:21 Russ Cox
2004-03-26 9:54 ` Douglas A. Gwyn
2004-03-26 12:32 ` Fco.J.Ballesteros
2004-03-26 15:41 ` Russ Cox
2004-03-26 15:48 ` Fco.J.Ballesteros
2004-03-26 17:39 ` Russ Cox
2004-03-27 13:07 ` boyd, rounin
2004-03-26 15:42 ` Russ Cox
2004-03-26 18:24 ` Scott Schwartz
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=40648187.6050901@swtch.com \
--to=rsc@swtch.com \
--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).