This is the mail archive of the gcc-patches@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]

Re: [pch] Fix largefile.c on sparc and sparc64


On Sun, Nov 07, 2004 at 12:56:14PM -0500, James A. Morrison wrote:
> 
> Jakub Jelinek <jakub@redhat.com> writes:
> 
> > On Sun, Nov 07, 2004 at 12:33:26PM -0500, James A. Morrison wrote:
> > > 
> > >  This fixes the largefile.c test cases on sparc and sparc64.  It doesn't fix
> > > all the failures on sparc64, but setting TRY_EMPTY_VM_SPACE to something
> > > off in never, never land for sparc64 doesn't fix those failures either.
> > 
> > Still you should IMHO set TRY_EMPTY_VM_SPACE to some > 4GB address for
> > defined(__sparc__) && defined(__LP64__)
> > and only use 0x60000000 for sparc32.
> > 
> > 	Jakub
> 
>  Ok, would it be better to use __LP64__ or __arch64__ ? 

__arch64__ is sparc64 specific while __LP64__ is more generic.
It doesn't matter much because we can't get rid of __arch64__
nor __LP64__ any time soon.
My personal preference would be __LP64__, but both options are fine.

	Jakub


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]