From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Sergei Gavrikov <sergei.gavrikov@gmail.com>
Cc: eCos Discussion <ecos-discuss@sourceware.org>
Subject: Re: [ECOS] place thread stack into CCM memory on STM32
Date: Fri, 17 Oct 2014 15:45:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1410171832520.2693@sg-laptop> (raw)
In-Reply-To: <alpine.DEB.2.00.1410171706110.1880@sg-laptop>
On Fri, 17 Oct 2014, Sergei Gavrikov wrote:
> On Fri, 17 Oct 2014, Oleg Uzenkov wrote:
>
> > Ok, it appears that it is possible to specify
> > __attribute__((section("<name>"))) for class's member methods.
>
> Really?
>
> https://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html says
>
> You may use the section attribute with initialized or uninitialized
> global variables.
Excuse too hasty response. It seemed for me you managed relocation that
_thread_stack[] and I cited FM on variable attributes.
Sergei
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2014-10-17 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 14:01 Oleg Uzenkov
2014-10-17 12:02 ` Oleg Uzenkov
2014-10-17 14:25 ` Sergei Gavrikov
2014-10-17 15:45 ` Sergei Gavrikov [this message]
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=alpine.DEB.2.00.1410171832520.2693@sg-laptop \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-discuss@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).