we made some simple tests with STM32F100 Value Line Eval Board:
//------------------------------------------------------------------------------ // Variables static unsigned char sDstBuf[1024]; // 1KiB static unsigned char sSrcBuf[sizeof(sDstBuf)];
printf("Copying words from misaligned src to aligned dst buffer... "); memset(sDstBuf, 0xcd, sizeof(sDstBuf));
with optimize Level 3, optimize for time this takes 120usec
with optimize Level 0 155usec
almost the same if memcpy is used: memcpy(sDstBuf, (const void *)0xcd, sizeof(sDstBuf));
It runs into hard fault, if optimize Level >=1 and optimise for time is not set.
I think this is a compiler error..
We ran into this before with MDK 4.60, now we use 4.70A
Werner
If you did read my post, and pondered a bit, you wouldn't "err, no" me.
A large percent of threads on this forum runs for a number of days.
Look at the time stamps of first/last post here - this is a young thread so _no_ answer here can be considered a late response.
Which was why I noted that the only way you could debate 'late' was if someone posted it late at night. But that requires that you know what time zone the person lives in.
You realize this is a web forum? Not a chat program where you get a 'beep' or something in the mobile phone, and then instantly writes a response?