From: Richard Shih-Ping Chan <cshihpin@dso.org.sg>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] For GCCv3: recommend -fno-builtin and remove -fvtable-gc
Date: Mon, 09 Jul 2001 18:35:00 -0000 [thread overview]
Message-ID: <20010710094111.A12594@cshihpin.dso.org.sg> (raw)
Hi eCos team - I would like to make two suggestions for GCC3
[1] Make -fno-builtin a default command line option.
This is to prevent unwanted optimisations of builtin functions
at the default optimisation level of -g -O2. An example is
the optimisation of printf and the consequent introduction of
extra symbols like putchar and puts by GCCv3.
This doesn't always link as some installs supply printf but not
putchar/puts. An example is the target+template pc+redboot.
At -O2 GCCv3 really seems to convert
some printf to putchar/puts statements.
This should have no untoward effect on GCC2.95.
[2] -fvtable-gc is no longer supported by GCCv3 but I'm not sure
what implications that has.
Cheers
Richard Chan <cshihpin@dso.org.sg>
next reply other threads:[~2001-07-09 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 18:35 Richard Shih-Ping Chan [this message]
2001-07-10 0:29 ` Andrew Lunn
2001-07-10 10:43 ` Jonathan Larmour
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=20010710094111.A12594@cshihpin.dso.org.sg \
--to=cshihpin@dso.org.sg \
--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).