Thanks for the help everyone.
I would like to begin working on this (== supporting this natively in
the compiler with a keyword/modifier (not sure about the correct term
:))).
What steps do I need to take before beginning in order to ensure this
effort will go into the main branch once it's comple
On 7/20/08, Joe Buck <[EMAIL PROTECTED]> wrote:
> On Sat, Jul 19, 2008 at 06:53:41PM -0400, Robert Dewar wrote:
> > Andi Kleen wrote:
> > Well the idea would be specifically for applications that can live
> > in 32 GB. If you compile in this mode, obviously you can't play
> > this trick, and you h
The application does go well beyond the 4GB range.
By using this implementation I can use 32-bit pointers for most
objects (those that do not require <8byte alignment, i.e. chars, etc.)
while still have a 32GB address range.
On 7/19/08, Robert Dewar <[EMAIL PROTECTED]> wrote:
> Y
s 2^3 (8),
// which provides access to addresses up to 2^35 (32GB).
//
// Note that if unaligned addresses, or addresses farther than the
allowed limit,
// are sent to aligned_ptr it will assert, and so while the user will have to
// rerun with full 64-bit pointers, there is no risk of memory corr
