From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Duncan Sands <baldrick@wanadoo.fr>, Andrew Morton <akpm@digeo.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BUGed to death
Date: Tue, 15 Apr 2003 07:35:44 -0700 [thread overview]
Message-ID: <69850000.1050417343@[10.10.2.4]> (raw)
In-Reply-To: <200304151401.00704.baldrick@wanadoo.fr>
>> Seems all these bug checks are fairly expensive. I can get 1%
>> back on system time for kernel compiles by changing BUG to
>> "do {} while (0)" to make them all compile away. Profiles aren't
>> very revealing though ... seems to be within experimental error ;-(
>
> What happens if you just turn BUG_ON into "do {} while (0)"?
I believe I already did that by turning BUG() into a null expression.
#define BUG_ON(condition)
do { if (unlikely((condition)!=0)) BUG(); } while(0)
The compiler should be smart enough to optimise that away, methinks.
M.
next prev parent reply other threads:[~2003-04-15 14:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 20:19 Martin J. Bligh
2003-04-14 20:40 ` Duncan Sands
2003-04-14 21:02 ` Dave Jones
2003-04-14 21:10 ` Duncan Sands
2003-04-14 21:17 ` Dave Jones
2003-04-15 11:57 ` Duncan Sands
2003-04-15 12:05 ` Dave Jones
2003-04-15 14:39 ` Martin J. Bligh
2003-04-23 15:08 ` Duncan Sands
2003-04-14 21:00 ` Dave Jones
2003-04-14 20:55 ` Martin J. Bligh
2003-04-14 21:08 ` Dave Jones
2003-04-14 21:50 ` Andrew Morton
2003-04-14 21:55 ` Dave Jones
2003-04-15 0:23 ` H. Peter Anvin
2003-04-15 12:01 ` Duncan Sands
2003-04-15 12:31 ` Jens Axboe
2003-04-15 12:36 ` Dave Jones
2003-04-15 12:40 ` Jens Axboe
2003-04-15 12:49 ` Sean Neakums
2003-04-15 12:52 ` Sean Neakums
2003-04-15 13:01 ` Roman Zippel
2003-04-15 13:17 ` Jens Axboe
2003-04-15 13:55 ` Duncan Sands
2003-04-15 14:22 ` Jens Axboe
2003-04-15 14:35 ` Martin J. Bligh [this message]
2003-04-15 14:39 ` Duncan Sands
2003-04-15 14:45 ` Martin J. Bligh
2003-04-15 14:58 ` Duncan Sands
2003-04-15 14:30 rwhron
2003-04-15 15:57 ` Dave Jones
2003-04-15 16:11 ` Nick Piggin
2003-04-15 16:42 ` Michael Buesch
2003-04-15 16:45 ` Dave Jones
2003-04-15 18:33 Chuck Ebbert
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='69850000.1050417343@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=akpm@digeo.com \
--cc=baldrick@wanadoo.fr \
--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
all inboxes | Powered by JetHome®