Re: How to detect that memory over 4G isn't available ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



En/na Paul Chavent ha escrit:
> Sorry for the lack of information.
> 
> I'am under a GNU/Linux, on an X86 platform. The problem is reproductible
> on an ubuntu 10.4 and on a slackware 13. On the slackware gcc --verbose
> gives :
> 
> Reading specs from /usr/lib/gcc/i486-slackware-linux/4.3.3/specs
> Target: i486-slackware-linux
> Configured with: ../gcc-4.3.3/configure --prefix=/usr --libdir=/usr/lib
> --enable-shared --enable-bootstrap
> --enable-languages=ada,c,c++,fortran,java,objc --enable-threads=posix
> --enable-checking=release --with-system-zlib
> --disable-libunwind-exceptions --enable-__cxa_atexit --enable-libssp
> --with-gnu-ld --verbose --with-arch=i486 --target=i486-slackware-linux
> --build=i486-slackware-linux --host=i486-slackware-linux
> Thread model: posix
> gcc version 4.3.3 (GCC)
> 

X86 (i486 here) architecture has a physical limit of 4Gb because it's a
32 bit architecture (and 2^32 == 4G addresses).

This may explain why you can't go beyond 4Gb.


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux