From: Andrew Morton <akpm@zip.com.au>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Hugh Dickins <hugh@veritas.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] BUG preserve registers
Date: Sat, 09 Feb 2002 21:28:55 -0800 [thread overview]
Message-ID: <3C660517.AAA7FA8@zip.com.au> (raw)
In-Reply-To: <3C65F523.FDDB7FA@zip.com.au> <Pine.LNX.4.33.0202092211001.10024-100000@home.transmeta.com>
Linus Torvalds wrote:
>
> On Sat, 9 Feb 2002, Andrew Morton wrote:
> >
> > This is due to BUG() calls in inline functions in headers. The biggest
> > culprit is dget(), in dcache.h. This causes the full path of the header file
> > to be expanded into each and every compilation unit which includes
> > dcache.h.
>
> Hmm. Which brings up another issue: can somebody come up with an idea of
> how to make the thing not use the whole pathname, but only the basename
> relative to the top-of-tree?
This is the cue for Keith to pop up and say "fixed in kbuild 2.5".
The preprocessor is simply pasting together its -I argument and the
string from the #include statement. There doesn't seem to be a way
of getting it to just emit "include/linux/dcache.h" or "drivers/char/serial.c".
__BASE_FILE__ seems to have been supported for a sufficiently long time. It
will just give us "dcache.h". I think that's OK. We don't get full path
info for the .c files either, and I'm not aware of that causing problems - if
there's a BUG() at inode.c:1234 we seem to be able to work out which inode.c
to look at.
__BASE_FILE__ is already used a bit in spinlock.h, so I think I'll
go with that. But I'll also take a look at all the inlined BUGs.
>
> Note that the correct thing to do may be to un-inline a lot of things.
> We've done that before, simply because it often improves performance.
>
> What ends up happening is that some function starts out really small, and
> then later on people add logic and debug code to it, and suddenly it's not
> really appropriate to inline any more.
I noticed :)
-
next prev parent reply other threads:[~2002-02-10 5:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-09 8:13 [PATCH] BUG preserve registers Hugh Dickins
2002-02-09 8:32 ` Andrew Morton
2002-02-09 10:33 ` Hugh Dickins
2002-02-09 19:30 ` Linus Torvalds
2002-02-09 19:34 ` Andrew Morton
2002-02-09 21:37 ` Linus Torvalds
2002-02-09 20:00 ` H. Peter Anvin
2002-02-09 21:49 ` Linus Torvalds
2002-02-09 20:24 ` H. Peter Anvin
2002-02-09 20:11 ` Andrew Morton
2002-02-09 20:15 ` Linus Torvalds
2002-02-09 22:07 ` Andrew Morton
2002-02-10 2:41 ` Alan Cox
2002-02-10 4:20 ` Andrew Morton
2002-02-10 4:23 ` H. Peter Anvin
2002-02-10 4:28 ` Andrew Morton
2002-02-10 6:16 ` Linus Torvalds
2002-02-10 5:28 ` Andrew Morton [this message]
2002-02-10 7:23 ` Linus Torvalds
2002-02-10 6:28 ` Andrew Morton
2002-02-10 9:05 ` Andrew Morton
[not found] ` <200202110710.g1B7A5t28328@Port.imtp.ilyichevsk.odessa.ua>
2002-02-11 7:22 ` Andrew Morton
2002-02-11 17:19 ` Hugh Dickins
2002-02-11 19:48 ` Andrew Morton
2002-02-11 20:52 ` Hugh Dickins
2002-02-10 7:13 ` H. Peter Anvin
2002-02-10 8:53 ` arjan
2002-02-11 15:26 ` Jamie Lokier
2002-02-10 6:23 ` Eric W. Biederman
2002-02-10 6:50 ` Andrew Morton
2002-02-10 15:40 ` Eric W. Biederman
2002-02-10 7:08 ` Stevie O
2002-02-10 14:35 ` Olaf Dietsche
2002-02-10 4:55 ` Linus Torvalds
2002-02-10 5:03 ` Linus Torvalds
2002-02-10 4:21 ` Brian Gerst
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=3C660517.AAA7FA8@zip.com.au \
--to=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.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.