Path: utzoo!telly!ddsw1!lll-winken!killer!mit-eddie!bloom-beacon!tut.cis.ohio-state.edu!CS.UTAH.EDU!ee-sno%wasatch From: ee-sno%wasatch@CS.UTAH.EDU (Niel Orcutt) Newsgroups: gnu.gcc.bug Subject: Re: Porting GNU CC 1.30 to VMS Message-ID: <8811281456.AA20423@wasatch.utah.edu> Date: 28 Nov 88 14:56:18 GMT Sender: daemon@tut.cis.ohio-state.edu Distribution: gnu Organization: GNUs Not Usenet Lines: 24 About Dr. Smart's problems with GCC 1.30 on VMS: I tried pretty much the same tricks as he did. I even went so far as to create a cross compiler on a large UNIX host and produce .s files, which I then assembled and linked on the VMS host. I used the c-parse_tab.c that came with the distribution. I had to upload the VMS include files to the UNIX host and use -I to point the cross compiler to them. I made a set of .s files with -O on and another set with -O off (also, remember to put -DPCC_ALIGNMENT in the command line). The resultant executable behaved just like the executable that I had previously created using GCC 1.22; it produced a register dump indicating that some function had tried to read through the NULL pointer. When creating an executable using GCC 1.22, I had to create c-parse_tab.s and then edit it to change an instruction of the form movab _,r2 This line appeared somewhere between line 10000 and 11000 in c-parse_tab.s. The varied from compilation to compilation. I replaced with "_hash_table.0", as I recall. This produced a linkable GCC with the warning that Dr. Smart mentioned. When I used the 1.30 cross compiler, this problem disappeared, but the warning remained. So, I gave up the effort also. Does anyone have working GCC 1.3x sources or binaries for VMS?