This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: What happens during optimization
- From: Gary Thomas <gthomas at ecoscentric dot com>
- To: Daniel Lidsten <Daniel dot Lidsten at combitechsystems dot com>
- Cc: eCos Discussion <ecos-discuss at sources dot redhat dot com>
- Date: 15 Nov 2002 07:53:20 -0700
- Subject: Re: [ECOS] What happens during optimization
- References: <004B1D7A5257174C9044A1B7BD0E60ED232C50@ratatosk.combitechsystems.com>
On Fri, 2002-11-15 at 07:47, Daniel Lidsten wrote:
> Hi,
>
> I have run my system on a debug version of eCos but now i want to try some optimization. I removed all debug info (-gdwarf) and added the flag -O2.
>
> When i link my application to the new eCos then i get some "undefined reference" regarding some thread functions like Cyg_Thread::self.
>
> The above function are probably removed due to the optimization and i was wondering if there are any way of forcing it to be a part of the final library?
Did you rebuild everything after you added the optimization option?
Note: optimization and debugging info (-gdwarf) can both be present
although debugging may be more difficult.
Note2: our default builds always use optimization.
--
------------------------------------------------------------
Gary Thomas |
eCosCentric, Ltd. |
+1 (970) 229-1963 | eCos & RedBoot experts
gthomas@ecoscentric.com |
http://www.ecoscentric.com/ |
------------------------------------------------------------
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss