[Bug target/40647] 32-bit pointers on 64-bit operating systems

2009-07-04 Thread rguenth at gcc dot gnu dot org
--- Comment #10 from rguenth at gcc dot gnu dot org 2009-07-04 19:18 --- "/Qauto-ilp32 (-auto-ilp32): Specifies that the application cannot exceed a 32-bit address space, which allows the compiler to use 32-bit pointers whenever possible." ^^^ so it does in fact not change

[Bug target/40647] 32-bit pointers on 64-bit operating systems

2009-07-04 Thread hjl dot tools at gmail dot com
--- Comment #9 from hjl dot tools at gmail dot com 2009-07-04 19:03 --- /Qauto-ilp32 (-auto-ilp32): Specifies that the application cannot exceed a 32-bit address space, which allows the compiler to use 32-bit pointers whenever possible. To use this option, you must also specify /Qipo [v

[Bug target/40647] 32-bit pointers on 64-bit operating systems

2009-07-04 Thread pinskia at gcc dot gnu dot org
--- Comment #8 from pinskia at gcc dot gnu dot org 2009-07-04 19:00 --- i guess this is a dup. *** This bug has been marked as a duplicate of 34764 *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/40647] 32-bit pointers on 64-bit operating systems

2009-07-04 Thread hjl dot tools at gmail dot com
--- Comment #7 from hjl dot tools at gmail dot com 2009-07-04 18:56 --- I think icc has an option to limit pointer size to 32bit. -- hjl dot tools at gmail dot com changed: What|Removed |Added ---

[Bug target/40647] 32-bit pointers on 64-bit operating systems

2009-07-04 Thread rguenth at gcc dot gnu dot org
--- Comment #6 from rguenth at gcc dot gnu dot org 2009-07-04 13:50 --- No, we have -mcmodel as well, but that only specifies the maximum size of the data and code segments and does not change the size of pointers (-mcmodel=small is the default btw). -- http://gcc.gnu.org/bugzilla/s

[Bug target/40647] 32-bit pointers on 64-bit operating systems

2009-07-04 Thread joseph at codesourcery dot com
--- Comment #5 from joseph at codesourcery dot com 2009-07-04 11:54 --- Subject: Re: 32-bit pointers on 64-bit operating systems The natural analogy would be with MIPS n32 (an ILP32 ABI for 64-bit MIPS hardware), which also indicates the directory names (/lib32) to use. There would c

[Bug target/40647] 32-bit pointers on 64-bit operating systems

2009-07-04 Thread tkoenig at gcc dot gnu dot org
--- Comment #4 from tkoenig at gcc dot gnu dot org 2009-07-04 11:34 --- This would be something like Intel's -mcmodel=small, see http://software.intel.com/sites/products/documentation/hpc/compilerpro/en-us/fortran/win/compiler_f/copts/common_options/option_mcmodel.htm -- http://gcc

[Bug target/40647] 32-bit pointers on 64-bit operating systems

2009-07-04 Thread rguenth at gcc dot gnu dot org
--- Comment #3 from rguenth at gcc dot gnu dot org 2009-07-04 11:02 --- Right, a new 32bit ABI would need to be defined with all its problems of introducing another multilib variant. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added --

[Bug target/40647] 32-bit pointers on 64-bit operating systems

2009-07-04 Thread tkoenig at gcc dot gnu dot org
--- Comment #2 from tkoenig at gcc dot gnu dot org 2009-07-04 10:16 --- (In reply to comment #1) > Very naive question: is it not what -m32 should do? The gcc info page states `-m32' `-m64' Generate code for a 32-bit or 64-bit environment. The 32-bit environment sets int, lo

[Bug target/40647] 32-bit pointers on 64-bit operating systems

2009-07-04 Thread dominiq at lps dot ens dot fr
--- Comment #1 from dominiq at lps dot ens dot fr 2009-07-04 10:07 --- Very naive question: is it not what -m32 should do? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40647