From: David Woodhouse <dwmw2@infradead.org>
To: Tim Walberg <twalberg@mindspring.com>
Cc: "J. Imlay" <jimlay@u.washington.edu>, linux-kernel@vger.kernel.org
Subject: Re: macro conflict
Date: Fri, 24 Aug 2001 14:03:34 +0100 [thread overview]
Message-ID: <14764.998658214@redhat.com> (raw)
In-Reply-To: <20010823143440.G20693@mindspring.com>
In-Reply-To: <20010823143440.G20693@mindspring.com> <Pine.A41.4.33.0108231150110.64144-100000@dante14.u.washington.edu>
twalberg@mindspring.com said:
> There has already been **much** discussion about this, but I think
> that the bottom line is that the new version is safer and more robust
> than the old version, and thus is not likely to be changed back.
That's a completely separate issue. You can fix it while keeping sane
semantics for min() and max().
#define real_min(x,y) ({ typeof((x)) _x = (x); typeof((y)) _y = (y); (_x>_y)?_y:_x; })
#define min(x,y) ({ if strcmp(STRINGIFY(typeof(x)), STRINGIFY(typeof(y))) BUG(); realmin(x,y) })
/me wonders if gcc would manage to optimise that.
--
dwmw2
next prev parent reply other threads:[~2001-08-24 13:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 19:03 macro conflict J. Imlay
2001-08-23 19:21 ` Alan Cox
2001-08-23 19:34 ` Tim Walberg
2001-08-23 20:01 ` Alan Cox
2001-08-23 20:02 ` raybry
2001-08-23 20:16 ` Magnus Naeslund(f)
2001-08-23 20:27 ` Alan Cox
2001-08-23 20:29 ` Magnus Naeslund(f)
2001-08-23 23:18 ` Andrew Cannon
2001-08-23 23:37 ` Magnus Naeslund(f)
2001-08-23 23:35 ` Roman Zippel
2001-08-24 1:42 ` Camiel Vanderhoeven
2001-08-24 13:03 ` David Woodhouse [this message]
2001-08-24 13:15 ` Keith Owens
2001-08-24 13:17 ` David Woodhouse
2001-08-24 14:20 ` Bill Pringlemeir
2001-08-24 21:17 ` Roman Zippel
2001-08-24 13:34 ` Richard B. Johnson
2001-08-24 18:20 ` David Wagner
2001-08-24 17:25 ` Alex Bligh - linux-kernel
2001-08-24 17:34 ` David Woodhouse
2001-08-24 18:12 ` Bill Pringlemeir
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=14764.998658214@redhat.com \
--to=dwmw2@infradead.org \
--cc=jimlay@u.washington.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=twalberg@mindspring.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox