Path: utzoo!attcan!uunet!ginosko!brutus.cs.uiuc.edu!jdevito
From: jdevito@brutus.cs.uiuc.edu (John Devitofranceschi)
Newsgroups: unix-pc.general
Subject: Gcc 1.36 Offer
Keywords: Binaries, ftp site needed
Message-ID: <1989Oct22.070945.29624@brutus.cs.uiuc.edu>
Date: 22 Oct 89 07:09:45 GMT
Sender: news@brutus.cs.uiuc.edu
Distribution: unix-pc
Organization: U of Illinois, CS Dept., Systems Research Group
Lines: 39


Well, after playing around with the macro call to "ASM_OUTPUT_SKIP" in 
final.c (that is to say, eliminating it and replacing it with what
was in 1.35 (for only final.c!)), I have what appears to be a 'working'
gcc 1.36.

I have put working in quotes because I noticed some weirdness going on
when I compiled the thing with itself the second time around (stage2):

	1) "cc1" got "fatal signal 9" seemingly randomly;
		the compiler would die once, but then 
		work fine after starting it again on a 
		given module.

	2) When I "cmp"'d the stage 2 object files with the final
		object files, there were 2 files that had differences.
		Blowing those two files away and recompiling them
		made everything work okay.

What I'd like to know is: has anyone else had these problems?

If you're desperate enough to have the binaries for gcc 1.36, you are
welcome to have some of mine.  If you maintain an anonymous ftp
unix-pc archive and would like to house these things for general
retrieval, please let me know. No one should have to put up with 
the hassle of getting this beast up and running once it's already
been done.

Again, please send me e-mail with requests to test drive the program,
give it a good home, or comment on the problems that I mentioned.
I'll summarize in a couple of weeks if I get lots o' responses.

cheers,
jd

-----------------------------------------------------------------------
John Devitofranceschi	    
jdevito@a.cs.uiuc.edu	   
(217) 332-2458