This is the mail archive of the ecos-patches@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug 1001142] User defined linker sections.


Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001142

--- Comment #2 from Ilija Kocho <ilijak@siva.com.mk> 2011-02-13 18:47:32 GMT ---
(In reply to comment #1)

Sergei

There has been discussion on this in bug 1001114 where user sections were
introduced, and this bug is an outcome of that discussion. Please refer to bug
1001114 for a complete evolution.

> I thought that's what. Another place where we could define SECTION_user
> macro could be lpc17xx variant linker include file, e.g.
> 
>   cortexm/lpc17xx/var/current/include/pkgconf/mlt_cortexm_lpc17xx.ldi

You'll find an example snippet here:
http://bugs.ecos.sourceware.org/attachment.cgi?id=1088
and here's a description:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001114#c7 

> 
> This definition could be included from the target's memory layout
> files.
> 
> - variant's source is a good place to comment what is macro for;
> 
> - no mess in architecture linker script, if that is a pain;
> 
> What do you think about such a compromise?

It is a considerable step to add new feature to an architecture and should be
carried out with caution. Technically, the macro shall perform it's function at
either place, probably more relevant questions are following:


  - Shall we need this kind of facility for other future variants and how
often?
  - Is the macro (as is or with reasonable modifications) generic enough to
enter at architecture level?

I am open for any resolution.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]