From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andrew Morton <akpm@zip.com.au>,
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: 09 Feb 2002 23:23:09 -0700 [thread overview]
Message-ID: <m1k7tl6ek2.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0202092211001.10024-100000@home.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0202092211001.10024-100000@home.transmeta.com>
Linus Torvalds <torvalds@transmeta.com> writes:
> 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?
>
> I doubt it is possible, but maybe there is some clever way to avoid it..
>
> > I'm showing thirteen header files, for a total of 83k. I'll do something
> > about this...
>
> Ok, so even your gcc obviously is _not_ intelligent enough to throw away
> strings from inline functions that aren't used. Oh well.
One possibility is to do something like:
ud2
.word __LINE__
.long 1f
.section __FILE__
.linkonce discard
1: .asciz __FILE__
.previous
Which will put each filename string in it's own section and let the
linker merge the duplicates. I don't know how to wrap all of this up
nicely in a inline asm statement but perhaps someone else can work
out the remaining details. Ideally I would put a prefix on the name
of all of the sections for easy processing, but string concatenation
doesn't work in asm :(
Eric
next prev parent reply other threads:[~2002-02-10 6:27 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
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 [this message]
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=m1k7tl6ek2.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=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.