RE: Porting gcc to HP Nonstop Ux

["praveen" <praveen dot khanna at wipro dot com>]

Hi Jim,

After using dis for comparison, I was able to overcome problems with
most
of the object files.
However, some object files 'dis' output still had differences. I removed
the optimization flag -O2 flag and overcame the problem. However, I
still see differences between fold-const.o generated from stage2 and
stage3.

Do you feel there are problems with my stage 2 build.

Thaks very much.
Praveen
------------------------------------------------------------------------
---------------
Praveen Khanna                       Tel:(91)-(80)-5732296(2020)
Wipro Technologies,                       98442-63812
#26,Hosur Main Road,               e-mail:praveen.khanna@wipro.com      
Bommanhalli,                  
Bangalore-68
"Kindness is in our power, even when fondness is not. 
-Samuel Johnson, lexicographer"
------------------------------------------------------------------------
----------------


-----Original Message-----
From: Jim Wilson [mailto:wilson@tuliptree.org] 
Sent: Friday, May 02, 2003 10:37 PM
To: praveen
Cc: 'Neil Booth'; 'praveen'; gcc-bugs@gcc.gnu.org
Subject: RE: Porting gcc to HP Nonstop Ux


On Fri, 2003-05-02 at 10:41, praveen wrote:
> I got the following message at the end of stage3:
> Bootstrap comparison failure!
> alias.o differs

>From your nm diff, it looks like the assembler is putting temporary file
names in the symbol table, and this is causing the diff to fail.  You
want to find a way to stop this.  Compile a file with -S and look at the
assembly output carefully.  If you are emitting the temp file name into
the output, perhaps in a .file directive, then that is a problem that
should be fixed.  If the assembler is doing this on its own, then
perhaps changing the assembler options will stop this.  If you aren't
emitting a .file directive, then perhaps that is the problem.

nm is sufficient for checking for object file differences.  Hopefully
when you did the bootstrap, you piped the make output into a file.  Pick
one of the files that is different, preferably a small one.  Pull the
stage1/xgcc and stage2/xgcc build commands for that file out of the make
output, and add -S options.  Then compare the assembly output files for
differences.

Jim