This is the mail archive of the gcc-help@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: casting on 64/32-bit environment

From: Tim Prince <tprince at computer dot org>
To: Andrew Haley <aph-gcc at littlepinkcloud dot COM>
Cc: Mitja Ursic <mitja dot ursic at email dot si>, gcc-help at gcc dot gnu dot org
Date: Tue, 23 Oct 2007 17:47:55 -0700
Subject: Re: casting on 64/32-bit environment
References: <20071022065835.68B048B751@www1.email.si> <18204.27649.345359.983376@zebedee.pink> <20071023130802.95E888B82A@www1.email.si> <18205.63184.863404.445882@zebedee.pink>

Andrew Haley wrote:

> Well, if this data structure is shared with FORTRAN you'll have to do
> something similar on the FORTRAN side.  It'll be a different type:
> INTEGER*8 or somesuch.  I'm not a FORTRAN programmer.
> 
> But yes, long will work on all gcc targets I'm aware of.

All maintained Fortran compilers, including gfortran, support c_ptr data
type.  You can't very well port intentionally non-portable stuff to a
different architecture unless you correct such anachronisms.

Follow-Ups:
- Re: casting on 64/32-bit environment
  - From: Andrew Haley

References:
- Re: casting on 64/32-bit environment
  - From: Mitja Ursic
- Re: casting on 64/32-bit environment
  - From: Andrew Haley
- Re: casting on 64/32-bit environment
  - From: Mitja Ursic
- Re: casting on 64/32-bit environment
  - From: Andrew Haley

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