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: m68k-coff: Unused memory region included in output file?

From: Bill Gatliff <bgat at billgatliff dot com>
To: Toralf Lund <toralf at procaptura dot com>,crossgcc <crossgcc at sources dot redhat dot com>
Date: Tue, 26 Oct 2004 10:20:13 -0500
Subject: Re: m68k-coff: Unused memory region included in output file?
References: <417E6692.3000302@procaptura.com> <417E67A5.7050502@billgatliff.com> <417E6944.5060905@procaptura.com>

Toralf:

Hmmm...

Does the program run properly when you munge your linker command file to leave this data out?

I think there was a .init section added in 3.x, along with a .ctor and .dtor that are needed even for non-C++ programs.

Bits of the dump you posted look like function addresses, which would be consistent with .ctor/.dtor tables.

I wouldn't know any of this if I hadn't had the exact same problem when I converted over to 3.x, but that was a long time ago and my program refused to run without the fixes...

b.g.

--
Bill Gatliff
Embedded GNU, Linux, and other board support packages.
bgat@billgatliff.com


------
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: m68k-coff: Unused memory region included in output file?
  - From: Toralf Lund

References:
- m68k-coff: Unused memory region included in output file?
  - From: Toralf Lund
- Re: m68k-coff: Unused memory region included in output file?
  - From: Bill Gatliff
- Re: m68k-coff: Unused memory region included in output file?
  - From: Toralf Lund

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