From: "Harsha D" <harshad@sanyo.co.in>
To: <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] which gcc toolchain to use ?
Date: Tue, 26 Jul 2005 09:21:00 -0000 [thread overview]
Message-ID: <C03A3C267DDF184EA523BBAB577BF92405B16E@blrexsr1.slti.sanyo.co.in> (raw)
Hi
I have been trying to port ecos on ARM9 based board.
I tried with gcc v4.0 (cygwin) and gcc v3.4.3
In my case i have observed that
in v4.0 >
Removing optimization(O2) flag... redboot works
Including optimization flag... redboot fails
in v3.4.2 >
Removing optimization flag... redboot FAILS
Including optimization flag... redboot works
also....redboot seems to hang at do_version, printing the RAM range.
I would like to know which is the best/suitable gcc toolchain to be used
with eCos
regards
harsha
--
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 reply other threads:[~2005-07-26 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 9:21 Harsha D [this message]
2005-07-26 9:49 ` Andrew Lunn
2005-07-26 13:06 ` Gary Thomas
2005-07-27 3:22 Harsha D
2005-07-27 7:16 ` Andrew Lunn
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=C03A3C267DDF184EA523BBAB577BF92405B16E@blrexsr1.slti.sanyo.co.in \
--to=harshad@sanyo.co.in \
--cc=ecos-discuss@ecos.sourceware.org \
/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).