From: David Woodhouse <dwmw2@infradead.org>
To: Hua Zhong <huaz@cs.columbia.edu>
Cc: Davide Libenzi <davidel@xmailserver.org>, linux-kernel@vger.kernel.org
Subject: Re: linux/macros.h(new) and linux/list.h(mod) ...
Date: Thu, 05 Jul 2001 22:58:53 +0100 [thread overview]
Message-ID: <9004.994370333@redhat.com> (raw)
In-Reply-To: <200107052154.RAA07008@razor.cs.columbia.edu>
In-Reply-To: <200107052154.RAA07008@razor.cs.columbia.edu>
huaz@cs.columbia.edu said:
> Doesn't it add more overhead? I think using inline functions are
> much better.
Why should it add overhead? Even the most naïve compiler ought to generate
the same code, surely? I must admit I haven't looked hard at the output -
it didn't even occur to me that it might produce suboptimal code.
> Yes you have to define it for different types (char, short, int,
> long, signed/unsigned).
Unfortunately, this being C means that you can't call them all by the same
name. If I have to use unsigned_long_max(x,y) I'd rather type it out myself
:)
--
dwmw2
next prev parent reply other threads:[~2001-07-05 21:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 20:57 linux/macros.h(new) and linux/list.h(mod) Davide Libenzi
2001-07-05 21:31 ` David Woodhouse
2001-07-05 21:45 ` Davide Libenzi
2001-07-05 21:54 ` Hua Zhong
2001-07-05 21:58 ` David Woodhouse [this message]
2001-07-05 22:20 ` Hua Zhong
2001-07-05 22:06 ` Davide Libenzi
2001-07-05 22:10 ` J . A . Magallon
2001-07-05 22:33 ` Daniel Phillips
2001-07-05 22:43 ` David Woodhouse
2001-07-05 22:53 ` Davide Libenzi
2001-07-05 23:23 ` J . A . Magallon
2001-07-05 22:57 ` Alan Cox
2001-07-05 23:05 ` Matthew Dharm
2001-07-05 23:07 ` Alan Cox
2001-07-05 23:08 ` David Woodhouse
2001-07-06 1:51 ` Arnaldo Carvalho de Melo
2001-07-05 23:21 ` Davide Libenzi
[not found] ` <0107060149080M.03760@starship>
2001-07-05 23:54 ` Daniel Phillips
2001-07-06 17:38 ` Neil Booth
2001-07-06 22:02 ` Arnaldo Carvalho de Melo
2001-07-05 22:03 ` Kai Germaschewski
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=9004.994370333@redhat.com \
--to=dwmw2@infradead.org \
--cc=davidel@xmailserver.org \
--cc=huaz@cs.columbia.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox