From: Jonathan Larmour <jifl@jifvik.org>
To: Gerster Jochen-B01096 <B01096@freescale.com>
Cc: ecos-patches@ecos.sourceware.org
Subject: Re: FW: eCos for MPC55xx
Date: Tue, 18 Jul 2006 16:46:00 -0000 [thread overview]
Message-ID: <44BD1047.8060507@jifvik.org> (raw)
In-Reply-To: <DF02D66C37C26B4C8018BF84F0E37FEC0D10A250@zwg18exm01.ea.freescale.net>
Gerster Jochen-B01096 wrote:
>
> The problem is: The POWERPC gcc compiler (allocated from the ecos site)
> optimize memcpy calls with small length, instead it uses its own inline
> function without taking care of aligned access.
If it did not work for unaligned accesses on PowerPC in general, then this
would have been discovered years ago.
Perhaps have the semantics of an opcode in the MPC55xx changed so that
something that used to work for all PowerPC now only works on aligned
addresses? If so that wouldn't be good, but it's not beyond the realms of
possibility.
> This is a very very big
> problem using the TCP/IP stack because the IP-address is 4byte so the
> gcc optimize and the offset of the IP-address in the different
> protocol-headers varies. This ends in a exception :(
>
> So I asking me now: I'm the only one with this problem? How do you solve
> this problem, perhaps a compiler flag?
Theoretically -fno-builtin can be used to disable GCC's optimisations if
they are genuinely at fault. But I'm not sure. Have you tried a small
testcase? And if so have you looked at the assembler GCC is producing?
Jifl
--
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
next prev parent reply other threads:[~2006-07-18 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 7:58 Gerster Jochen-B01096
2006-07-18 16:46 ` Jonathan Larmour [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-20 8:21 Gerster Jochen-B01096
2006-07-21 15:50 ` Ilija Koco
2006-07-05 7:01 Gerster Jochen-B01096
2006-07-05 8:23 ` Ilija Koco
2011-06-15 8:29 ` scratch45
2011-06-15 9:21 ` Christophe Coutand
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=44BD1047.8060507@jifvik.org \
--to=jifl@jifvik.org \
--cc=B01096@freescale.com \
--cc=ecos-patches@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).