All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Hugh Dickins <hugh@veritas.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [2/2] Change p[gum]d_clear_* inlines to macros to fix p?d_ERROR
Date: Sat, 10 Sep 2005 16:44:55 +0200	[thread overview]
Message-ID: <200509101644.55887.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0509101440420.14979@goblin.wat.veritas.com>

On Saturday 10 September 2005 16:15, Hugh Dickins wrote:
> On Sat, 10 Sep 2005, Andi Kleen wrote:
> > Change p[gum]d_clear_* inlines to macros to fix p?d_ERROR
> >
> > When this code was refactored by Hugh it was moved out of the actual
> > functions into these inlines. The problem is that pgd_ERROR
> > uses __FUNCTION__ and __LINE__ to show where the error happened,
> > and with the inline that is pretty meaningless now because
> > it's the same for all callers.
> >
> > Change them to be macros to avoid this problem
>
> Please don't.  It adds much less than I misremember (only 550 bytes
> to my i386 PAE config), but even so it's a waste of space. 

Hmm? Macros and inlines take the same amount of space. 


>
> (Of course, I was emboldened to make those changes because the messages
> had never been seen in living memory, beyond our own private development
> screwups.  They started appearing just around the time I changed them.)

I have actually seen them while debugging something. But it was useless. That 
is why I made the change.

-Andi

  reply	other threads:[~2005-09-10 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-10 12:04 [2/2] Change p[gum]d_clear_* inlines to macros to fix p?d_ERROR Andi Kleen
2005-09-10 14:15 ` Hugh Dickins
2005-09-10 14:44   ` Andi Kleen [this message]
2005-09-10 15:02     ` Hugh Dickins

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=200509101644.55887.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --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 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.