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 09:51:00 -0000 [thread overview]
Message-ID: <20110215095049.0FABE2F78003@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 #20 from Ilija Kocho <ilijak@siva.com.mk> 2011-02-15 09:50:42 GMT ---
(In reply to comment #18)
> (In reply to comment #16 and comment #17)
>
> Ilija, thank you for clarifications and snippets. I get it. However I
> would rename the undescored macros (__CYG_USER_SECTION_*), e.g.
>
> #define CYG_LINK_SECTION_START(_name_) __ ## _name_ ## _start
> #define CYG_LINK_SECTION_END(_name_) __ ## _name_ ## _end
>
> Variants of prefixes to discuss CYG_LINK, CYG_LOAD, and CYG_LD. That
> will mean, - Use them in a linker scripts.
>
> #define CYG_USER_SECTION_START(_name_) CYG_LINK_SECTION_START(_name_)
> #define CYG_USER_SECTION_END(_name_) CYG_LINK_SECTION_END(_name_)
>
> The USER means, - Use in a userspace code.
I'm not quite convinced about this notation, I consider USER_SECTION a stem for
all related macro names. I decided to prefix concatenation with __ because they
are supposed to be kind of "hidden", but it may be just my view.
However if some of "linker" variants is opted I would prefer LD as this acronym
is associated with linker staff through the code (target.ld, mlt*.ldi, etc).
>
> About duplication the declarations. As target.ld scripts ends with
>
> #include <pkgconf/hal_arch.h>
> #include CYGHWR_MEMORY_LAYOUT_LDI
>
> We would declare USER_SECTION after that inclusion the arch's header
> and that can be a place for standalone declaration:
>
> #include <pkgconf/hal_arch.h>
> #if defined(CYG_LINK_SECTION_START) && defined(CYG_LINK_SECTION_END)
> #define USER_SECTION(_name_, _region_, _vma_, _lma_) \
> ._name_ _vma_ : _lma_ \
> { CYG_LINK_SECTION_START(_name_) = ABSOLUTE (.); \
> *(._name_*) \
> CYG_LINK_SECTION_END(_name_) = ABSOLUTE (.); } \
> > _region_
> #endif
>
> #include CYGHWR_MEMORY_LAYOUT_LDI
>
> So, the place to define CYG_{USER,LINK} macros would be hal_cortexm.h.
> I hope that I did not "break" something again :-)
I'm not sure if it is proper to place such stuff in a file generated from CDL.
--
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 9:51 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 [this message]
2011-02-15 12:28 ` bugzilla-daemon
2011-02-15 15:00 ` bugzilla-daemon
2011-02-15 21:00 ` bugzilla-daemon
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=20110215095049.0FABE2F78003@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).