From: byron@netapp.com (Byron Rakitzis)
To: dalibor@immd3.informatik.uni-erlangen.de, rc@hawkwind.utcs.toronto.edu
Subject: Re: gcc-2.3.1 -O2 corrupts rc?
Date: Tue, 1 Dec 1992 01:41:15 -0500 [thread overview]
Message-ID: <9212010641.AA18635@netapp.netapp.com> (raw)
re: gcc. I don't have gcc-2.3 here, you are on your own. Given how
flaky new GNU code is I wouldn't be surprised if it's an optimizer
bug. BTW, you don't mention the architecture you are using.
>P.S. Browsing through the rc-list-file that came with the distribution I have
> to suppose that the author of rc gave up working on it; archone.tamu.edu
> seems to have ceased ftp-service.
> Is there a place where fixes to rc are archived or who (if anybody)
> maintains rc now?
re: me. I'm still here, as byron@netapp.com. Mail to the old address
*should* be forwarded here. If it isn't, please let me know!
re: fixes. rc-1.5 should be out eventually. Let me get es out of my
hair first. The fact that 1.4 is so stable is a disincentive for me to
work hard on 1.5, btw. However, I am keeping a track of all the (so far
minor) changes that need to be made. Unless I have an unexpected amount
of spare time on my hands, I'm hoping to have something by mid-winter.
re: archives. Chris Siebenmann is of course taking care of this at
Toronto. Thanks Chris! I'm wondering whether a note to this effect
should be posted to the net? i.e., something that will get propagated
to comp.archives.
re: archone.tamu.edu. Apparently Texas A&M University has seen it fit
to ignore all ftp and telnet from off-site. Nice move. I guess it fits
in well with their academic mission, something like that. (Pardon my
cynicism, but this is worse than Stanford turning off fingerd on their
general-access machines (like leyland))
Byron.
next reply other threads:[~1992-12-01 6:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-12-01 6:41 Byron Rakitzis [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-11-27 17:01 Stefan Dalibor
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=9212010641.AA18635@netapp.netapp.com \
--to=byron@netapp.com \
--cc=dalibor@immd3.informatik.uni-erlangen.de \
--cc=rc@hawkwind.utcs.toronto.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).