public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001814] Kinetis clock gating
Date: Sun, 07 Apr 2013 10:41:00 -0000	[thread overview]
Message-ID: <bug-1001814-104-jiEKvJZiHB@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1001814-104@http.bugs.ecos.sourceware.org/>

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001814

--- Comment #21 from Ilija Kocho <ilijak@siva.com.mk> ---
(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
> code.
> 
> However, if anyone has any idea how it could have worked, please enlighten
> me.

Mike
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).

Ilija

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2013-04-07 10:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 19:43 [Bug 1001814] New: " bugzilla-daemon
2013-04-04 19:44 ` [Bug 1001814] " bugzilla-daemon
2013-04-04 19:57 ` bugzilla-daemon
2013-04-06  5:49 ` bugzilla-daemon
2013-04-06  6:17 ` bugzilla-daemon
2013-04-06 12:47 ` bugzilla-daemon
2013-04-06 12:49 ` bugzilla-daemon
2013-04-06 13:06 ` bugzilla-daemon
2013-04-06 13:54 ` bugzilla-daemon
2013-04-06 13:57 ` bugzilla-daemon
2013-04-06 14:00 ` bugzilla-daemon
2013-04-06 14:08 ` bugzilla-daemon
2013-04-06 14:21 ` bugzilla-daemon
2013-04-06 14:24 ` bugzilla-daemon
2013-04-06 14:37 ` bugzilla-daemon
2013-04-06 14:54 ` bugzilla-daemon
2013-04-06 15:47 ` bugzilla-daemon
2013-04-06 16:34 ` bugzilla-daemon
2013-04-06 17:21 ` bugzilla-daemon
2013-04-06 17:40 ` bugzilla-daemon
2013-04-07  5:39 ` bugzilla-daemon
2013-04-07  7:13 ` bugzilla-daemon
2013-04-07 10:41 ` bugzilla-daemon [this message]
2013-04-07 13:52 ` bugzilla-daemon
2013-04-07 14:19 ` bugzilla-daemon
2013-04-07 16:44 ` bugzilla-daemon
2013-04-15 22:29 ` bugzilla-daemon

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=bug-1001814-104-jiEKvJZiHB@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --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).