This is the mail archive of the
mailing list for the eCos project.
[Bug 1001814] Kinetis clock gating
- From: bugzilla-daemon at bugs dot ecos dot sourceware dot org
- To: unassigned at bugs dot ecos dot sourceware dot org
- Date: Sun, 07 Apr 2013 10:41:36 +0000
- Subject: [Bug 1001814] Kinetis clock gating
- Auto-submitted: auto-generated
- References: <bug-1001814-777 at http dot bugs dot ecos dot sourceware dot org/>
Please do not reply to this email, use the link below.
--- Comment #21 from Ilija Kocho <firstname.lastname@example.org> ---
(In reply to comment #20)
> I printed out dlmalloc.cxx before I retired for the day and read some of the
> description. I can't understand how this code with the large malloc ever
> worked. Given the 26K heap, and the allocation up to 4K chunks, no chunk
> should ever have been large enough unless it can append chunks, which my
> understanding is that it can't do that.
> Given that, I don't think I have any choice but to rewrite my algorithm to
> use a 4K buffer.
> So I can't find any reason not to commit this code, even if it breaks my
> However, if anyone has any idea how it could have worked, please enlighten
If the buffer is permanent, you may use staticaly allocated array. Also, FYI
Cortex-M specification requires stack to be 8 Byte aligned (though I haven't
experienced any anomaly with 4 Byte alignment so far).
You are receiving this mail because:
You are the assignee for the bug.