Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Paul Bame <bame@noam.fc.hp.com>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: alan@linuxcare.com.au (Alan Modra),
	marteaut@esiee.fr, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Include trouble
Date: Tue, 28 Nov 2000 12:27:09 -0700	[thread overview]
Message-ID: <E140qPF-0005T4-00@noam.fc.hp.com> (raw)
In-Reply-To: Your message of "Tue, 28 Nov 2000 12:37:28 EST." <200011281737.MAA24142@hiauly1.hia.nrc.ca>

= Hmm.  Most 32 bit systems use "unsigned int" rather than "unsigned long".

I will be happy to change it back to unsigned int.  The only reason
I used unsigned long is because it seems off_t wants to be, to a
first approximation, the word length of the machine, and 'long' does
that.

= Using "unsigned long" might cause problems with packages like libio.


= I know there is a problem if off_t is not the same as size_t.

What problem is that?  I'm working on a proposal for the palinux
type sizes at the moment.

One dilema is that off_t is supposed to
be good for file offsets, which these days means it should be 64 bits.
size_t refers to the sizes of objects which are expected to fit in
RAM, so should be the word size of the machine.  So there's a conflict
because one logic suggests 64-bit off_t and 32-bit size_t on 32-bit palinux,
but your statement suggests they should be the same size.  Any ideas?

However I'm leaning towards leaning with the older 32-bit off_t because
we might not want to be the first ones to fix all the problems with
making it 64 bits on a 32-bit machine.

	-P

  reply	other threads:[~2000-11-28 19:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-27 20:31 [parisc-linux] Include trouble Thomas Marteau
2000-11-28  4:59 ` Alan Modra
2000-11-28  9:19   ` Alan Modra
2000-11-28 17:37     ` John David Anglin
2000-11-28 19:27       ` Paul Bame [this message]
2000-11-28 20:02         ` Alan Cox
2000-11-28 21:21           ` Paul Bame
2000-11-28 21:58             ` Alan Cox
2000-11-28 20:24         ` John David Anglin
2000-11-28 20:33           ` John David Anglin
2000-11-28 23:27       ` Alan Modra
2000-11-28 15:07 ` [parisc-linux] Mouse driver for PS/2 Thomas Marteau
2000-11-28 17:21   ` Helge Deller
2000-11-28 19:30     ` Thomas Marteau
2000-11-28 20:41       ` Helge Deller
2000-11-28 17:49   ` Grant Grundler

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=E140qPF-0005T4-00@noam.fc.hp.com \
    --to=bame@noam.fc.hp.com \
    --cc=alan@linuxcare.com.au \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=marteaut@esiee.fr \
    --cc=parisc-linux@thepuffingroup.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox