From: Grant Edwards <grante@visi.com>
To: chris.r.lipchik@att.net
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] allocating code to sections in source code
Date: Sat, 27 Jan 2001 14:48:00 -0000 [thread overview]
Message-ID: <20010127165211.A9119@visi.com> (raw)
In-Reply-To: <20010127213259.EHSQ25609.mtiwmhc21.worldnet.att.net@webmail.worldnet.att.net>
On Sat, Jan 27, 2001 at 09:32:58PM +0000, chris.r.lipchik@att.net wrote:
> I'm looking for a reference guide on line which would
> have the proper syntax for allocating code in a C or
> ASM source file to a specific section which can be later
> referenced by the linker. Specifially, I'm interested in
> the syntax for the gcc.
In assembly, use the .section directive:
.section foobar
<your stuff here>
In gcc, use the __attribute__(()) mechanism:
char myBuffer[512] __attribute__((section("foobar")));
Both of these are explained in the "info" files:
$ info gcc
$ info gas
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2001-01-27 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 13:33 chris.r.lipchik
2001-01-27 14:48 ` Grant Edwards [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-27 7:29 chris.r.lipchik
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=20010127165211.A9119@visi.com \
--to=grante@visi.com \
--cc=chris.r.lipchik@att.net \
--cc=ecos-discuss@sourceware.cygnus.com \
/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).