* [ECOS] compiling options
@ 2001-04-05 12:16 Rafael RodrÃguez Velilla
2001-04-05 12:52 ` Dan Conti
2001-04-05 12:56 ` Jonathan Larmour
0 siblings, 2 replies; 5+ messages in thread
From: Rafael RodrÃÂguez Velilla @ 2001-04-05 12:16 UTC (permalink / raw)
To: ecos
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
I have seen some options that are default in eCos while compiling for
which I can't find documentation. these are:
-fdata-sections
-fno-rtti
-fno-exceptions
-fvtable-gc
-finit-priority
-Wl,--gc-sections
Can somebody tell me what are they for or where is the documentation
about those?
I have also read that ffunction-sections is used but I don't
understand why. It seems to generate worse code, which is its advantage?
--
Rafael RodrÃguez Velilla rrv@tid.es
Telefónica I+D http://www.tid.es
Telf: +34 - 91 337 4270
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: [ECOS] compiling options
2001-04-05 12:16 [ECOS] compiling options Rafael RodrÃguez Velilla
@ 2001-04-05 12:52 ` Dan Conti
2001-04-06 2:26 ` Rafael RodrÃguez Velilla
2001-04-06 2:45 ` Hugo 'NOx' Tyson
2001-04-05 12:56 ` Jonathan Larmour
1 sibling, 2 replies; 5+ messages in thread
From: Dan Conti @ 2001-04-05 12:52 UTC (permalink / raw)
To: ecos
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
> I have seen some options that are default in eCos while compiling for
> which I can't find documentation. these are:
> -fdata-sections
> -fno-rtti
> -fno-exceptions
> -fvtable-gc
> -finit-priority
> -Wl,--gc-sections
>
> Can somebody tell me what are they for or where is the documentation
> about those?
http://www.gnu.org/manual/
check out the manual for gcc, it has information about various command line
options.
>
> I have also read that ffunction-sections is used but I don't
> understand why. It seems to generate worse code, which is its advantage?
-ffunction-sections causes functions to be put in their own section. used in
conjunction with --gc-sections, you get selective linking, so that functions
that aren't called aren't linked in to your final image.
-Dan
>
> --
> Rafael RodrÃguez Velilla rrv@tid.es
> Telefónica I+D http://www.tid.es
> Telf: +34 - 91 337 4270
>
>
>
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [ECOS] compiling options
2001-04-05 12:52 ` Dan Conti
@ 2001-04-06 2:26 ` Rafael RodrÃguez Velilla
2001-04-06 2:45 ` Hugo 'NOx' Tyson
1 sibling, 0 replies; 5+ messages in thread
From: Rafael RodrÃÂguez Velilla @ 2001-04-06 2:26 UTC (permalink / raw)
To: ecos
Thank you all for the information. I thought that the man pages that where
installed while I compiled the toolchain should be the most uptodate of my
particular tools.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [ECOS] compiling options
2001-04-05 12:52 ` Dan Conti
2001-04-06 2:26 ` Rafael RodrÃguez Velilla
@ 2001-04-06 2:45 ` Hugo 'NOx' Tyson
1 sibling, 0 replies; 5+ messages in thread
From: Hugo 'NOx' Tyson @ 2001-04-06 2:45 UTC (permalink / raw)
To: ecos-discuss
danc@iobjects.com (Dan Conti) writes:
> > I have also read that ffunction-sections is used but I don't
> > understand why. It seems to generate worse code, which is its advantage?
>
> -ffunction-sections causes functions to be put in their own section. used in
> conjunction with --gc-sections, you get selective linking, so that functions
> that aren't called aren't linked in to your final image.
That's right.
It will also mean that individual .o files, and libraries &c *are* larger.
But that has nothing to do with the *code* in the final image.
Is that why it looked like worse code?
- Huge
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [ECOS] compiling options
2001-04-05 12:16 [ECOS] compiling options Rafael RodrÃguez Velilla
2001-04-05 12:52 ` Dan Conti
@ 2001-04-05 12:56 ` Jonathan Larmour
1 sibling, 0 replies; 5+ messages in thread
From: Jonathan Larmour @ 2001-04-05 12:56 UTC (permalink / raw)
To: Rafael RodrÃÂguez Velilla; +Cc: ecos
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
Rafael RodrÃguez Velilla wrote:
>
> I have seen some options that are default in eCos while compiling for
> which I can't find documentation. these are:
> -fdata-sections
> -fno-rtti
> -fno-exceptions
See http://gcc.gnu.org/onlinedocs/gcc_3.html for these and
-ffunction-sections
The -fno-exceptions is the opposite of -fexceptions - it disables C++
exceptions support.
> -fvtable-gc
Garbage collect unused C++ vtable entries.
> -finit-priority
C++ constructor priorities. Required for eCos.
> -Wl,--gc-sections
"-Wl," means it is passed to the linker. See:
http://sources.redhat.com/binutils/docs-2.10/ld_2.html#SEC2
> I have also read that ffunction-sections is used but I don't
> understand why. It seems to generate worse code, which is its advantage?
Why do you think so?
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2001-04-06 2:45 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-04-05 12:16 [ECOS] compiling options Rafael RodrÃguez Velilla
2001-04-05 12:52 ` Dan Conti
2001-04-06 2:26 ` Rafael RodrÃguez Velilla
2001-04-06 2:45 ` Hugo 'NOx' Tyson
2001-04-05 12:56 ` Jonathan Larmour
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).