This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

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: Output file size?

From: Toralf Lund <toralf at procaptura dot com>
To: Peter Barada <pbarada at mail dot wm dot sps dot mot dot com>
Cc: crossgcc at sources dot redhat dot com
Date: Thu, 18 Sep 2003 16:42:39 +0200
Subject: Re: Output file size?
References: <3F69AD22.4080602@procaptura.com> <200309181430.h8IEUC013535@hyper.wm.sps.mot.com>

Peter Barada wrote:

Any idea why gcc's output is that much larger? Is there any way I can reduce the size? Note that -Os helps a bit, but I suspect that it actually destroys the code (asm() isn't handled correctly.)
How does GCC 'destroy' the 68k code when using -Os?  An example would be
quite appreciative.

Inline assembly code (specified via asm()) is simply missing from the assembly file generated by 'm68k-coff-gcc -Os -S'. At least, that what it looks like for one of my actual C files. I'll try with a simplified example...

- Toralf

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

Follow-Ups:
- Re: Output file size?
  - From: Toralf Lund

References:
- Output file size?
  - From: Toralf Lund
- Re: Output file size?
  - From: Peter Barada

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