Searched hist:219741 (Results 1 - 6 of 6) sorted by relevance

/freebsd-10.0-release/sys/ia64/ia64/
H A Dunaligned.cdiff 219741 Fri Mar 18 13:46:34 MDT 2011 marcel Use VM_MAXUSER_ADDRESS rather than VM_MAX_ADDRESS when we talk about
the bounds of user space. Redefine VM_MAX_ADDRESS as ~0UL, even though
it's not used anywhere in the source tree.
H A Dsupport.Sdiff 219741 Fri Mar 18 13:46:34 MDT 2011 marcel Use VM_MAXUSER_ADDRESS rather than VM_MAX_ADDRESS when we talk about
the bounds of user space. Redefine VM_MAX_ADDRESS as ~0UL, even though
it's not used anywhere in the source tree.
H A Dgenassym.cdiff 219741 Fri Mar 18 13:46:34 MDT 2011 marcel Use VM_MAXUSER_ADDRESS rather than VM_MAX_ADDRESS when we talk about
the bounds of user space. Redefine VM_MAX_ADDRESS as ~0UL, even though
it's not used anywhere in the source tree.
H A Dtrap.cdiff 219741 Fri Mar 18 13:46:34 MDT 2011 marcel Use VM_MAXUSER_ADDRESS rather than VM_MAX_ADDRESS when we talk about
the bounds of user space. Redefine VM_MAX_ADDRESS as ~0UL, even though
it's not used anywhere in the source tree.
H A Dmachdep.cdiff 219741 Fri Mar 18 13:46:34 MDT 2011 marcel Use VM_MAXUSER_ADDRESS rather than VM_MAX_ADDRESS when we talk about
the bounds of user space. Redefine VM_MAX_ADDRESS as ~0UL, even though
it's not used anywhere in the source tree.
/freebsd-10.0-release/sys/ia64/include/
H A Dvmparam.hdiff 219741 Fri Mar 18 13:46:34 MDT 2011 marcel Use VM_MAXUSER_ADDRESS rather than VM_MAX_ADDRESS when we talk about
the bounds of user space. Redefine VM_MAX_ADDRESS as ~0UL, even though
it's not used anywhere in the source tree.

Completed in 372 milliseconds