From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001142] User defined linker sections.
Date: Tue, 15 Feb 2011 21:00:00 -0000 [thread overview]
Message-ID: <20110215210048.1E9C02F78003@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001142-104@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001142
--- Comment #23 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2011-02-15 21:00:43 GMT ---
Hi
(In reply to comment #22)
> Sometimes the solution is doing nothing or next to nothing.
Fortunately, it happens sometimes.
> Since method for production of section boundaries is fixed,
> straight-forward and common (for all sections): __<section_name>_start
> __<section_name>_end, it could be documented (possibly within
> http://ecos.sourceware.org/docs-latest/ref/hal- linker-scripts.html )
> with some code snippet for zeroing of section.
>
> I guess USER_SECTION() would need a proper documentation anyway.
Honestly, I could not grasp why you need START/END macros (then you have
convinced me). The first picture in my head was. A HAL/MLT designer (not
CT user) using USER_SECTION macro "describes" a few random access memory
regions for new CPU. For example, 'mem1', 'mem2', 'mem3' sections. This
HAL/MLT designer provides and a support to init (clear) the regions, so,
he/she knows the names. It is clear to him/her to use __mem1_start,
__mem1_end, etc. as external labels (he/she knows what USER_SECTION()
macro is). He/she is the HAL designer. Then if they want they can
provide via CDL rules a few choices for CT user, for example, to obtain
some rooms in one from a few (one from from one) section (I mean a choice
the values are allowed by our designer), i.e. with CDL func. legal_values
{ mem1 mem2 mem3 }, I dislike an idea to allow CT user to name the
sections and "to code" in C/CPP using "complex" macros. But, this is mine.
So, we can stay on USER_SECTION() innovation only. What your verdict be?
Will HAL/MLT designer be happy with it? As for me I like this rollback.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-02-15 21:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 15:43 [Bug 1001142] New: " bugzilla-daemon
2011-02-03 17:02 ` [Bug 1001142] " bugzilla-daemon
2011-02-13 17:40 ` bugzilla-daemon
2011-02-13 18:47 ` bugzilla-daemon
2011-02-13 19:02 ` bugzilla-daemon
2011-02-13 19:50 ` bugzilla-daemon
2011-02-13 20:02 ` bugzilla-daemon
2011-02-14 7:28 ` bugzilla-daemon
2011-02-14 8:36 ` bugzilla-daemon
2011-02-14 9:17 ` bugzilla-daemon
2011-02-14 12:34 ` bugzilla-daemon
2011-02-14 12:44 ` bugzilla-daemon
2011-02-14 13:03 ` bugzilla-daemon
2011-02-14 13:16 ` bugzilla-daemon
2011-02-14 13:43 ` bugzilla-daemon
2011-02-14 15:52 ` bugzilla-daemon
2011-02-14 18:34 ` bugzilla-daemon
2011-02-14 21:06 ` bugzilla-daemon
2011-02-14 21:20 ` bugzilla-daemon
2011-02-14 22:02 ` bugzilla-daemon
2011-02-14 22:42 ` bugzilla-daemon
2011-02-15 9:51 ` bugzilla-daemon
2011-02-15 12:28 ` bugzilla-daemon
2011-02-15 15:00 ` bugzilla-daemon
2011-02-15 21:00 ` bugzilla-daemon [this message]
2011-02-15 22:38 ` bugzilla-daemon
2011-02-16 9:50 ` bugzilla-daemon
2011-02-16 10:11 ` bugzilla-daemon
2011-02-16 12:00 ` bugzilla-daemon
2011-02-16 12:15 ` bugzilla-daemon
2011-02-17 0:09 ` bugzilla-daemon
2011-02-17 14:19 ` bugzilla-daemon
2011-02-17 14:50 ` 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=20110215210048.1E9C02F78003@mail.ecoscentric.com \
--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).