This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gcc cross mips output sizes, 2.95.3 vs 3.3.3


David Wuertele <dave-gnus@bfnet.com> writes:
>>> I looked through the CSiBE website and the latest download tar.gz but
>>> I could not find any mention of what mips they are targeting.  Anyone
>>> here know?
>
> Eric> IIRC it's mips-elf.
>
> It does say mips-elf on the website.  I am using mipsel --- that
> shouldn't make a difference, should it?

But it looks like you're compiling for mipsel-_linux-gnu_ rather than
mipsel-_elf_.  That makes a hell of a difference.  mips-elf output is
non-PIC and is designed to run in a "bare-metal" environment.

Also, I see you're using g++ to compile jpeg-6b, with is C code.  Does
CSiBE do the same thing?  It makes a difference because you're comparing
the size of the object file (not the size of the .text section, as Zack
suggests you should do).  g++ will add unwind information by default
whereas gcc won't.

Richard


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]