All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [RFC] Introduce module API to QEMU
Date: Fri, 03 Apr 2009 07:59:00 -0500	[thread overview]
Message-ID: <49D60814.9020703@codemonkey.ws> (raw)
In-Reply-To: <Pine.LNX.4.64.0904030741020.2308@linmac.oyster.ru>

malc wrote:
> 4.1.2 comes from C90
>   

C99 would be a more reasonable thing to quote from since it updates C89.

>> So this is exactly the sort of thing that the standard is there to 
>> protect :-)
>>     
>
> No. Those are reserved for _any_ use. For example, 6.2.5 states:
>
>      31) An implementation may define new keywords that provide
>          alternative ways to designate  a  basic  (or  any  other)
>          type;  this does not violate the requirement that all
>          basic   types   be   different.    Implementation-defined
>          keywords  shall  have  the form of an identifier reserved
>          for any use as described in 7.1.3.
>   

I still think you're missing the fact that this is a variable that's 
provided by the compiler.  It's a GCC extension in the same way 
__attribute__ is.  The reason we have to declare the variables is 
because it's actually provided by the linker so GCC the front-end has no 
knowledge of these variables existence.

This isn't standard C99 but it certainly doesn't violate C99 either.

Regards,

Anthony Liguori

  reply	other threads:[~2009-04-03 12:59 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
2009-04-03  3:48     ` malc
2009-04-03 12:59       ` Anthony Liguori [this message]
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=49D60814.9020703@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.