Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Christoph Hellwig <hch@infradead.org>,
		Roman Zippel <zippel@linux-m68k.org>,
		David Brown <dmlb2000@gmail.com>,
		Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
		gdb@sourceware.org
Subject: Re: PAGE_SIZE Availability Inconsistency
Date: Thu, 08 Mar 2007 16:08:00 -0000	[thread overview]
Message-ID: <20070308160852.GB9916@infradead.org> (raw)
In-Reply-To: <1173369229.3550.2.camel@laptopd505.fenrus.org>

On Thu, Mar 08, 2007 at 07:53:49AM -0800, Arjan van de Ven wrote:
> > > > PAGE_SIZE should not be available at all.  Please use getpagesize()
> > > > instead.
> > > 
> > > While I agree, NBPG is a bit of a problem, although it's only needed for aout 
> > > coredumps AFAICT, but still needed to compile e.g. gdb.
> > 
> > So we should export this one with an arbitrary value (on multiple page
> > size architectures) and a warning, maybe even an __deprecated attached to
> > it.
> 
> if we think the kernel should export this one, we could do
> 
> #ifndef __KERNEL__
> #define PAGE_SIZE getpagesize()
> #endif

No, no no.  We should never export PAGE_SIZE.  We might export NBPG
as deprecated symbol for gdb if it really needs it, but that should
happen only on a.out systems, and it it should be a true constant,
not depending on PAGE_SIZE.

I've Cc'ed the gdb list on whether they have any comments on this
issue.


       reply	other threads:[~2007-03-08 16:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9c21eeae0703051555x1884fd7cse7968a71ec04eb27@mail.gmail.com>
     [not found] ` <20070306092917.GA5226@infradead.org>
     [not found]   ` <200703080318.04631.zippel@linux-m68k.org>
     [not found]     ` <20070308090031.GB7373@infradead.org>
     [not found]       ` <1173369229.3550.2.camel@laptopd505.fenrus.org>
2007-03-08 16:08         ` Christoph Hellwig [this message]
2007-03-08 16:22           ` Daniel Jacobowitz
2007-03-08 17:09           ` H. Peter Anvin
2007-03-08 17:12             ` Christoph Hellwig
2007-03-08 17:59             ` Anton Blanchard
2007-03-08 18:06               ` H. Peter Anvin
2007-03-08 21:44                 ` Anton Blanchard
2007-03-08 21:47                   ` Anton Blanchard
2007-03-08 21:48                   ` David Miller
2007-03-09  2:44                     ` Anton Blanchard
2007-03-09  4:20                       ` H. Peter Anvin
     [not found]                         ` <20070308.202718.68040662.davem@davemloft.net>
2007-03-09  4:32                           ` H. Peter Anvin
2007-03-09  4:36                             ` David Miller
2007-03-21  2:12                             ` Anton Blanchard
2007-03-21  2:52                               ` H. Peter Anvin
2007-03-08 22:17                   ` H. Peter Anvin
2007-03-08 21:04               ` David Brown

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=20070308160852.GB9916@infradead.org \
    --to=hch@infradead.org \
    --cc=arjan@infradead.org \
    --cc=dmlb2000@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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