> There was a prink in the inequivalent alias detector that printed > task->comm (that's the process name) if you add it back it will give > more information. Will add and rerun GCC testsuite. > > >From a kernel perspective, we need to avoid multiple maps of the same > > memory page with inequivalent virtual addresses (i.e., the maps must > > start at the same address & 0x3fffff). > > If I understand what you've done: you already patched the kernel to > force MAP_FIXED onto this boundary. If that's the case, the actual > problem must be an offset mapping; meaning something maps a region and > then maps a subregion of it. I've got to guess this is the dynamic > loader. This only occurs for MAP_FIXED and MAP_SHARED. MAP_FIXED alone still maps at the address specified by the application. 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
