Re: HPPA and Squeeze
- To: firstname.lastname@example.org (Randolph Chung)
- Cc: James.Bottomley@HansenPartnership.com, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
- Subject: Re: HPPA and Squeeze
- From: "John David Anglin" <email@example.com>
- Date: Mon, 6 Jul 2009 09:28:33 -0400 (EDT)
- Message-id: <[🔎] 20090706132836.B39E6500D@hiauly1.hia.nrc.ca>
- In-reply-to: <[🔎] 4A518DBD.firstname.lastname@example.org> from "Randolph Chung" at Jul 6, 2009 01:38:05 pm
> >>>>> I seem to recall that the kernel mmap implementation on hppa is somewhat
> >>>>> unique.
> >>>> I don't recall anything, Kyle?
> >>> This came up with respect to the GCC PCH implementation for parisc. See
> >>> comments in host-hpux.h. At the moment, we do have a PCH related bug.
> >>> See PR 39355. While I know the problem is present in the PCH file, I
> >>> haven't been able to figure out how wrong data gets in the file.
> There are some limitations on hppa if a file is both opened for reading
> (via read()) and written to via a mmap'ed mapping. This came up a few
> years ago.
> Does gcc do this?
Not that I am aware of. The situation is essentially the reverse of
the above. Data is written from a region of memory. Then, in another
instance of gcc, it needs to be mmap'ed back to the same location in
memory. In theory, it could be brought back to a different location
but this would require a fairly complex set of relocations.
J. David Anglin email@example.com
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)