From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: "Øyvind Harboe" <oyvind.harboe@zylin.com>
Cc: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] extern __inline__ and optimisation problems
Date: Wed, 21 Oct 2009 18:41:00 -0000 [thread overview]
Message-ID: <20091021184130.GA5952@sg-laptop> (raw)
In-Reply-To: <c09652430910210950q22b9beb5vebd98291dd247c4f@mail.gmail.com>
On Wed, Oct 21, 2009 at 06:50:26PM +0200, Ãyvind Harboe wrote:
> On Wed, Oct 21, 2009 at 6:15 PM, Sergei Gavrikov
> <sergei.gavrikov@gmail.com> wrote:
[snip]
> > Search: gcc 4 extern inline
> > http://gcc.gnu.org/gcc-4.3/porting_to.html
> >
> > May be that's it.
>
> It almost certainly is... Thanks for the tip!
>
> Does this really mean that *all* those places in eCos have to
> be touched to become compatible with the -std=c99 or -std=gnu99
> options?
>
> Ouch.
Greping the list on C99, I can repeat following you, Ouch :-) As I
could understand eCos LIBC is not ready to be C99 compliant. Recent
bird was Uwe's cdl_option CYGIMP_LIBC_STDIO_C99_SNPRINTF, but, it
seems your dreams about eCos modularity via DVCS is near future to
have some "C99" branch of the eCos language/c/libc. Ouch! But, may be
it won't be _too_ hard to play with these CDLs for start
grep ^cdl.*INLINE ecos.ecc | wc -l
22
Certainly, if I did not miss something in your message.
Yet another what I found from man gcc-4.3 is -fgnu89-inline. Well, you
have a full control on your own CFLAGS and I hope you have a time for a
digging and let us to know a solution, please.
Sergei
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-10-21 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 9:57 Øyvind Harboe
2009-10-21 13:59 ` Sergei Gavrikov
2009-10-21 15:16 ` Øyvind Harboe
2009-10-21 15:40 ` Sergei Gavrikov
2009-10-21 16:05 ` Øyvind Harboe
2009-10-21 16:15 ` Sergei Gavrikov
2009-10-21 16:50 ` Øyvind Harboe
2009-10-21 18:41 ` Sergei Gavrikov [this message]
2009-10-22 7:43 ` Øyvind Harboe
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=20091021184130.GA5952@sg-laptop \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=oyvind.harboe@zylin.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).