All of lore.kernel.org
 help / color / mirror / Atom feed
From: ramsdell@mitre.org (John D. Ramsdell)
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Use stddef.h in Mini-OS to define size_t
Date: 02 May 2006 05:41:47 -0400	[thread overview]
Message-ID: <ogt3bfshig4.fsf@divan.mitre.org> (raw)
In-Reply-To: <2b20bb71f6da14a494eab4d0ac9631f7@cl.cam.ac.uk>

Keir Fraser <Keir.Fraser@cl.cam.ac.uk> writes:

> Don't you get horrible namespace collisions when linking with a C
> library replacement? Not just stddef.h, but what about the
> definitions in minios's include/lib.h?

I received no compiler warnings other than the reported problem with
size_t and NULL.  The console source file includes lib.h before it
includes Lua headers, so the other definitions must fit with Lua's
definitions.  The functions in lib.c take precedence over the ones in
the C library, so they better be good.  The definition of gettimeofday
also overrides that which is provided by the C library, which is good
because the C library simply provides a stub routine.  By the way, the
Lua allocator in the modified version of console.c does not free
enough.  I did that to look for malloc bugs, but forgot to remove the
change when it made no difference.

John

  reply	other threads:[~2006-05-02  9:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1FaZpb-00044N-Hs@host-192-168-0-1-bcn-london>
2006-05-01 15:10 ` [PATCH] Use stddef.h in Mini-OS to define size_t John D. Ramsdell
2006-05-01 15:59   ` Keir Fraser
2006-05-01 20:52     ` John D. Ramsdell
2006-05-02  7:51       ` Keir Fraser
2006-05-02  9:41         ` John D. Ramsdell [this message]
2006-05-02  9:45           ` Keir Fraser
2006-05-02 12:45             ` Grzegorz Milos

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=ogt3bfshig4.fsf@divan.mitre.org \
    --to=ramsdell@mitre.org \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.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 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.