All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Weber <weber@nyc.rr.com>
To: linux-kernel@vger.kernel.org
Subject: More errors compiling kernel with GCC 3.1
Date: Wed, 02 Jan 2002 23:50:33 -0500	[thread overview]
Message-ID: <3C33E319.5010206@nyc.rr.com> (raw)

I'm just trying to read the source code, and I am having trouble in a 
few areas.  For example, I am completely baffled by the number of macros 
that get called in some places.  For example, in the semaphore code... 
just wondering why DECLARE_MUTEX (macro) calls DECLARE_SEMAPHORE_GENERIC 
(macro) calls SEMAPHORE_INITIALIZER (macro) calls 
WAIT_QUEUE_HEAD_INITIALIZER (macro) and so on, and so on...

I guess I can understand the use of a macro to deal with the overhead
introduced by calling functions all over the place, but having this
many macros that call macros isn't clear to me... I just hope that it
wasn't done to make the code easier to read or something :).

Can anyone point me to some documentation that might explain this type 
of thing?


             reply	other threads:[~2002-01-03  4:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-03  4:50 John Weber [this message]
     [not found] <fa.cast4mv.l0adg7@ifi.uio.no>
2002-01-03  4:58 ` More errors compiling kernel with GCC 3.1 John Weber

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=3C33E319.5010206@nyc.rr.com \
    --to=weber@nyc.rr.com \
    --cc=linux-kernel@vger.kernel.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.