From: Gary Thomas <gthomas@cambridge.redhat.com>
To: Colin Ford <colin.ford@pipinghotnetworks.com>
Cc: ecos-discuss@sources.redhat.com, bartv@redhat.com
Subject: Re: [ECOS] waitpid and alarm?
Date: Tue, 16 Jan 2001 07:46:00 -0000 [thread overview]
Message-ID: <XFMail.20010116084543.gthomas@cambridge.redhat.com> (raw)
In-Reply-To: <200101161536.PAA08774@colinf.pipinghotnetworks.com>
On 16-Jan-2001 Colin Ford wrote:
> Thanks for the info Bart. The only thing is that I was put off somewhat
> by the gcc info on the two option -ffunction-sections and
> -fdata-sections,
> see the last paragraph below:
>
> @item -ffunction-sections
> @itemx -fdata-sections
> Place each function or data item into its own section in the output
> file if the target supports arbitrary sections. The name of the
> function or the name of the data item determines the section's name
> in the output file.
>
> Use these options on systems where the linker can perform optimizations
> to improve locality of reference in the instruction space. HPPA
> processors running HP-UX and Sparc processors running Solaris 2 have
> linkers with such optimizations. Other systems using the ELF object format
> as well as AIX may have these optimizations in the future.
>
> Only use these options when there are significant benefits from doing
> so. When you specify these options, the assembler and linker will
> create larger object and executable files and will also be slower.
> You will not be able to use @code{gprof} on all systems if you
> specify this option and you may have problems with debugging if
> you specify both this option and @samp{-g}.
>
>
> Nice to know what you think of this?
>
Hogwash?
Honestly, the text is probably quite old and certainly does not reflect
our experience in using these options with eCos.
next prev parent reply other threads:[~2001-01-16 7:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 5:51 Colin Ford
2001-01-16 6:36 ` Bart Veer
2001-01-16 7:38 ` Colin Ford
2001-01-16 7:46 ` Gary Thomas [this message]
2001-01-16 9:52 ` Jonathan Larmour
2001-01-17 5:33 ` Colin Spier
2001-01-16 8:19 ` Bart Veer
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.20010116084543.gthomas@cambridge.redhat.com \
--to=gthomas@cambridge.redhat.com \
--cc=bartv@redhat.com \
--cc=colin.ford@pipinghotnetworks.com \
--cc=ecos-discuss@sources.redhat.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).