From: Gary Thomas <gthomas@cygnus.co.uk>
To: Dan Hovang <dan.hovang@cpen.com>
Cc: eCos Discussion <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Building rommable images for the AEB-1C
Date: Fri, 07 Jan 2000 07:19:00 -0000 [thread overview]
Message-ID: <XFMail.000107081914.gthomas@cygnus.co.uk> (raw)
In-Reply-To: <3875FBB9.C424300D@cpen.com>
I haven't seen this myself, so there may be something different in
our setups.
Can you send me the [binary] images? Then I can have our tools guys
look at them to see what the problem is.
On 07-Jan-00 Dan Hovang wrote:
> Gary Thomas wrote:
>>
>> You really should use *all* of the options used by the standard eCos
>> setup. In particular, these options tell the linker to throw away any
>> unused code. In your test case, this amounts to more than 100K bytes!
>> The image I build fits in ROM, even in the meager 32K defined as
>> default.
>
> The --gc-sections linkoption seems to corrupt the debuginfo, though.
>
> When using -ffunction-sections -fdata-sections with compile and
> --gc-sections with link and trying to connect with gdb i got:
>
> (gdb) target remote com1
> Remote debugging using com1
> 0xec78 in breakinst () at include/new:27
> 27 include/new: No such file or directory.
>
> without -Wl,--gc-sections I get:
>
> (gdb) target remote com1
> Remote debugging using com1
> 0x136a4 in breakinst ()
> at ecos/packages/hal/arm/arch/v1_2_1/src/hal_misc.c:204
> 204 HAL_BREAKPOINT(breakinst);
> Current language: auto; currently c
>
> Perhaps I'm missing some other option?
>
> The compiler options are:
>
> -g -O2 -Wall -Wpointer-arith -Winline -Wundef -Wstrict-prototypes
> -Woverloaded-virtual -fno-rtti -fno-exceptions -fvtable-gc
> -ffunction-sections -fdata-sections
>
> And link options are:
>
> -g -nostdlib -Wl,-static
>
> I'm using ecosSWtools-arm-990321. I've also tried using the Insigth
> 19991222 snapshot.
>
> /Dan
>
next prev parent reply other threads:[~2000-01-07 7:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF7B928FC7.8F137C30-ON8025685E.005316F3@ivesco.co.uk>
2000-01-06 7:15 ` Gary Thomas
2000-01-07 6:46 ` Dan Hovang
2000-01-07 7:19 ` Gary Thomas [this message]
[not found] <OF3C6DA87D.CDC4B358-ON8025685E.004A10DF@ivesco.co.uk>
2000-01-06 6:45 ` Gary Thomas
2000-01-06 5:40 Nicholas_Clarey
-- strict thread matches above, loose matches on Subject: below --
2000-01-06 4:38 Nicholas_Clarey
2000-01-06 5:00 ` Gary Thomas
2000-01-06 6:50 ` Grant Edwards
2000-01-06 7:01 ` Gary Thomas
2000-01-06 7:03 ` Dan Hovang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=XFMail.000107081914.gthomas@cygnus.co.uk \
--to=gthomas@cygnus.co.uk \
--cc=dan.hovang@cpen.com \
--cc=ecos-discuss@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).