rsync - Mar 2002 - Suspicious sizes by different C compilers

Hi all,
On my Alpha box running Tru64 5.1, rsync-2.5.4 compiled by GNU gcc
3.0.1 anh GNU make 3.79.1 has this size: 4562848.
The same version of rsync compiled by Compaq C compiler V6.3-028 and
Compaq make has this size: 655424.
It is about _7 times_ smaller!

I did a quick test and they seem both working OK.

Is that normal to see a huge difference in binary size produced by gcc
and vendor's C compilers?
Is there any comprehensive test suite so I can test the rsync to make
sure it works before installing into a production server?

Regards,
-- 
Zoong Pham                        zpham@mercy.com.au
UNIX Systems Administrator        Mercy Health and Aged Care Inc.

To get my PGP public key, email me with the subject:
Request for Zoong Pham's PGP public key
-------------- next part --------------
------------------------------------------------------------
If you are not the intended  recipient of this communication
please delete and destroy all copies immediately. If you are
the intended recipient of this communication, you should not
copy, disclose or distribute  this communication without the
authority of the sender.

Any views expressed  in this communication  are those of the
individual sender,  except  where  the  sender  specifically
states them to be the views of the Company.

If  you  have  received  this  email  in error or have other
concerns  regarding  this  transmission,  please contact the
Mercy Health & Aged Care Mail Administrator. 

                 Mercy Health & Aged Care 
         support@mercy.com.au  or  +613 9270 2600 
------------------------------------------------------------

On 19 Mar 2002, Zoong Pham <dpham@mercy.com.au>
wrote:
> Hi all,
> On my Alpha box running Tru64 5.1, rsync-2.5.4 compiled by GNU gcc
> 3.0.1 anh GNU make 3.79.1 has this size: 4562848.
> The same version of rsync compiled by Compaq C compiler V6.3-028 and
> Compaq make has this size: 655424.
> It is about _7 times_ smaller!
On gcc, rsync builds by default with debug symbols included.  If you
strip both executables, they should end up about the same size.
> Is there any comprehensive test suite so I can test the rsync to
> make sure it works before installing into a production server?
There is "make check", but it is not yet as comprehensive as it should
be.  If you'd like to contribute additional test cases that would be
great.

-- 
Martin

On 19 Mar 2002, "Granzow, Doug (NCI)" <granzowd@mail.nih.gov>
wrote:
> >On gcc, rsync builds by default with debug symbols included.  If you
> >strip both executables, they should end up about the same size.
> 
> 
> How do you "strip" an executable?  
Use "make install-strip", or see the manual for your system's
"strip"
command. 

  # strip /usr/bin/rsync
> Would doing this reduce the amount of memory rsync uses or improve
> its performance?
No, having debug symbols should not make a significant difference with
gcc on modern systems, as far as I know.  The pages containing debug
symbols will not be loaded into memory until they're touched. 

-- 
Martin