From: Gerster Jochen-B01096 <B01096@freescale.com>
To: ecos-patches@ecos.sourceware.org
Subject: FW: eCos for MPC55xx
Date: Thu, 06 Jul 2006 07:58:00 -0000 [thread overview]
Message-ID: <DF02D66C37C26B4C8018BF84F0E37FEC0D10A250@zwg18exm01.ea.freescale.net> (raw)
Hi Andrew
Ok so lets start with the memcpy problem, while I take care of the Copyright assignment.
Perhaps a new thread?
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. 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?
I solved this by renaming the ecos memcpy function to my_memcpy and define a macro in the string.h which link every memcpy to my_memcpy (#define memcpy my_memcpy). So the gcc don't touch this new function and .... No exceptions
Jochen
-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch]
Sent: Mittwoch, 5. Juli 2006 18:42
To: Gerster Jochen-B01096
Subject: Re: eCos for MPC55xx
On Wed, Jul 05, 2006 at 09:12:07AM +0200, Gerster Jochen-B01096 wrote:
>
> I can't belive it!! It works!?! :)
>
> So any idea how to public the source files??
> The mailing list seems to dislike the attached zip file?
Hi Jochen
As suggested send it as a number of packages. When presented with a big patch i tend to put it to the bottom of the pile because i know it will need a lot of effort. Lots of small, independent patches get handled quicker.
We will need a copyright assignment. Please take a look on the eCos website for the document you need to find.
Lastly, im on holiday until the beginning of August, so i don't expect i will be able to take a look at this until then. Maybe one of the other maintainers will handle it before then.
Andrew
next reply other threads:[~2006-07-06 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 7:58 Gerster Jochen-B01096 [this message]
2006-07-18 16:46 ` Jonathan Larmour
-- 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=DF02D66C37C26B4C8018BF84F0E37FEC0D10A250@zwg18exm01.ea.freescale.net \
--to=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).