> >>>>> 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. Dave -- J. David Anglin dave.anglin@xxxxxxxxxxxxxx National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
