gcc 1.33 compiled and working fine on UNIX pc/3B1

[Roger Florkowski]

In article <594 at icus.islp.ny.us> lenny at icus.islp.ny.us (Lenny Tropiano) writes:
>After all the problems I had compiling gcc 1.32 on my UNIX pc, I decided
>to ftp the diffs from prep.mit.edu for 1.32->1.33.  I ran them through
>patch, upgrading my 1.32 to 1.33.  After that chugged along for quite
>some time, I started the "make" ... 
>
>The compiler compiled flawlessly with the stock UNIX pc compiler (except
>that I am already running the gnu-cpp (C Preprocessor) that will handle
>the high amount of #defines that the GNU C compiler requires).  Then
>I recompiled the GNU C compiler with the compiled version of the compiler.
>This compiled up fine as well!  I was amazed .. no errors.  Maybe we're
>finally at a "stable version" of this compiler.
>

Last week I posted an article about gcc-1.32 working on my machine.
Over the weekend I picked up the diffs to gcc-1.33.  It bootstrapped
perfectly.  I have tested it on many public domain programs, and
I have yet to find one that didn't work.  All of the gcc compiled
executibles are smaller than the cc compiled ones.

A hint on using gcc:

some programs 'like' it better if you use these flags:

gcc -traditional -fwritable-strings

If you find a program that doesn't compile, or behaves badly after
compiled, try using these flags.

-traditional	affects gnu-cpp.  Produces identical output to /lib/cpp
		ALSO UNDEFINES __STDC__  (this might fix some "newer" programs)

-fwritable-strings	affects what gcc does with character strings.
			/lib/ccom allowed writable strings. (read man-page)


-- 
Roger Florkowski	       		{uunet!uvm-gen, attmail}!banzai!roger
The People's Computer Company			  `Revolutionary Programming'