This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
OK, so if I would like to use the full 64 bits where possible, but to be able to link with things built with the 32 bit compiler, what should I do?
GCC on recent Solaris/SPARC versions can produce 32-bit or 64-bit code, with the runtime switches -m32 or -m64, independently of whether it is itself a 32-bit (sparc-sun-solaris2*) or a 64-bit application (sparc64-sun-solaris2*). So this latter choice doesn't really affect what you can do with the compiler.
The 64-bit compiler is slower and bigger than the 32-bit compiler as of
3.4.x on typical UltraSPARC processors, so I personally think that the default (32-bit) is the best choice.
So I should ignore the entries in the docs about sparc64 then. I'll try that. At the moment I have a downloaded binary version that works. but I can't get a binary of binutils-2.15 so I'll probably not get much chance to try this out for a while. Anyone hoping (!) for further reports from me about this shouldn't hold their breath.:-)
Hugh
-- Eric Botcazou
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |