public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: Richard Shih-Ping Chan <cshihpin@dso.org.sg>,
	ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] For GCCv3: recommend -fno-builtin and remove -fvtable-gc
Date: Tue, 10 Jul 2001 10:43:00 -0000	[thread overview]
Message-ID: <3B4B3EC4.CA6AB0ED@redhat.com> (raw)
In-Reply-To: <20010710092918.H344@biferten.ma.tech.ascom.ch>

Andrew Lunn wrote:
> 
> On Tue, Jul 10, 2001 at 09:41:11AM -0800, Richard Shih-Ping Chan wrote:
> > 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.
> 
> I don't think this is a good idea. Some of the build in functions are
> optimized for the particular architecture, eg memcpy, memset,
> etc. They will be faster than the equivelent in the eCos library.
> 
> Is there a -fno-builtin-printf command line option? Just turn off that
> feature. The other option would be to rename printf in redboot, so the
> optimizer does not recognise it.

Yes we have plans to rename Redboot's printf, but in Redboot's short
lifetime it has already become quite pervasive.

In any case, we recommend avoiding GCC v3 on all targets where 2.95 support
exists. GCC v3 is not very stable for most embedded targets.

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
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

      reply	other threads:[~2001-07-10 10:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-09 18:35 Richard Shih-Ping Chan
2001-07-10  0:29 ` Andrew Lunn
2001-07-10 10:43   ` Jonathan Larmour [this message]

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=3B4B3EC4.CA6AB0ED@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=andrew.lunn@ascom.ch \
    --cc=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).