From: Anthony Liguori <aliguori@us.ibm.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [RFC] Introduce module API to QEMU
Date: Thu, 02 Apr 2009 22:36:04 -0500 [thread overview]
Message-ID: <49D58424.7050605@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0904030626380.4765@linmac.oyster.ru>
malc wrote:
> Once again ISO/IEC 9899:1990 4.1.2
>
I don't see a 4.1.2... Section 4 is "Conformance".
> ISO/IEC 9899:1999 7.1.3
>
At any rate, I assume you're referring to:
> +extern module_init_fn __start_initfuncs[], __stop_initfuncs[];
> +extern module_exit_fn __start_exitfuncs[], __stop_exitfuncs[];
All sections have variable definitions that define their start and stop
that are in the form __start_SECTION and __stop_SECTION. The
__attribute__((section("initfuncs"), used)) directive adds a new section
(if necessary) named initfuncs and the linker will create these
variables. If you look closely, the patch doesn't define these
variables, it just declares them because they're defined by the linker.
So this is exactly the sort of thing that the standard is there to
protect :-)
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-04-03 3:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 2:12 [Qemu-devel] [RFC] Introduce module API to QEMU Anthony Liguori
2009-04-03 2:29 ` malc
2009-04-03 3:36 ` Anthony Liguori [this message]
2009-04-03 3:48 ` malc
2009-04-03 12:59 ` Anthony Liguori
2009-04-03 17:00 ` malc
2009-04-03 17:31 ` Anthony Liguori
2009-04-03 17:46 ` malc
2009-04-03 17:59 ` M. Warner Losh
2009-04-03 17:58 ` M. Warner Losh
2009-04-03 18:05 ` Anthony Liguori
2009-04-03 20:12 ` Kevin Wolf
2009-04-03 18:30 ` malc
2009-04-03 7:08 ` Mark McLoughlin
2009-04-03 13:01 ` Anthony Liguori
2009-04-03 17:36 ` Anthony Liguori
2009-04-03 7:50 ` Avi Kivity
2009-04-03 11:35 ` Paul Brook
2009-04-03 12:57 ` Anthony Liguori
2009-04-03 13:09 ` Paul Brook
2009-04-03 14:10 ` Anthony Liguori
2009-04-03 14:11 ` Anthony Liguori
2009-04-03 14:28 ` Paul Brook
2009-04-03 14:53 ` Avi Kivity
2009-04-03 16:15 ` Anthony Liguori
2009-04-03 17:12 ` Blue Swirl
2009-04-03 14:04 ` Daniel Jacobowitz
2009-04-03 14:54 ` Avi Kivity
2009-04-03 15:10 ` Paul Brook
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=49D58424.7050605@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=av1474@comtv.ru \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).