From: Felipe Balbi <me@felipebalbi.com>
To: gcc-help@gcc.gnu.org
Cc: iant@google.com
Subject: Re: Figuring out start and end of sections
Date: Wed, 14 Apr 2010 06:21:00 -0000 [thread overview]
Message-ID: <20100414062234.GB4285@gandalf> (raw)
[-- Attachment #1: Type: text/plain, Size: 65 bytes --]
Added back the list. Sorry for that, I had forgotten.
--
balbi
[-- Attachment #2: Type: message/rfc822, Size: 1825 bytes --]
From: Felipe Balbi <me@felipebalbi.com>
To: Ian Lance Taylor <iant@google.com>
Subject: Re: Figuring out start and end of sections
Date: Wed, 14 Apr 2010 09:17:33 +0300
Message-ID: <20100414061733.GA4285@gandalf>
Hi Ian,
I guess my mailer is fishy, didn't get your mail either
Ian Taylor <iant@google.com> writes:
>> is there any way to figure out where a section starts and ends ?
>>
>> I added a specific section to my program using
>> __attribute__((section "<section name>")) and now I want to figure out
>> where that section starts so I can iterate over it and call the
>> function
>> pointers I'm adding to it.
>>
>> Do I need a specific linker script to achieve that or does the default
>> scripts give me possibility to find that out ?
>
> If you are using the GNU linker, or gold, and you make the section
> name a valid C identifier, then the linker will automatically define
> symbols __start_SECNAME and __stop_SECNAME which you can use.
so you're saying that something if I name my section _init then I should
have __start__init and __stop__init identifiers ??
The following isn't compiling:
#include <stdio.h>
typedef int (*initcall_t)(void);
static int my_init(void)
{
printf("hello world from _init\n");
}
static initcall_t __my_initcall_my_init
__attribute__((__used__))
__attribute__((section("_initcall"))) = my_init;
int main(int argc, char *argv[])
{
initcall_t *fn;
for (fn = __start__initcall; fn <
__stop__initcall; fn++)
(void) fn();
return 0;
}
do I need to pass any particular option to gcc/ld to get that working ??
--
balbi
next reply other threads:[~2010-04-14 6:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 6:21 Felipe Balbi [this message]
2010-04-14 6:30 ` Felipe Balbi
2010-04-14 6:47 ` Felipe Balbi
2010-04-14 6:50 ` Fabian Cenedese
-- strict thread matches above, loose matches on Subject: below --
2010-04-13 17:40 Felipe Balbi
2010-04-13 17:44 ` Andrew Haley
2010-04-14 0:24 ` Ian Lance Taylor
2010-04-14 8:49 ` Andrew Haley
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=20100414062234.GB4285@gandalf \
--to=me@felipebalbi.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.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).