This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran 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: 64/32 bit problems..

From: "Christopher D. Rickett" <crickett at lanl dot gov>
To: FX Coudert <fxcoudert at gmail dot com>
Cc: fortran at gcc dot gnu dot org
Date: Fri, 21 Jul 2006 14:45:38 -0600 (MDT)
Subject: Re: 64/32 bit problems..
References: <Pine.LNX.4.58.0607211415210.32196@lennox.lanl.gov> <44C13B90.5050700@gmail.com>

i guess i'm confused.  i want to step through the compilation by running 
f951 in the debugger, and i wasn't aware that you could pass -m32 right to 
f951 (it seems to ignore it).

On Fri, 21 Jul 2006, FX Coudert wrote:

> >  i am trying to run the
> > code through the debugger, but the 64 bit builds work as expected, and i'm
> > not sure how to give f951 the -m32 flag.  is there an easy way to do this?
> 
> I'd say -m32:
> 
> $ gfortran -v -m32 a.f90
> [...]
>  /usr/libexec/gcc/i386-redhat-linux/4.1.1/f951 a.f90 -quiet -dumpbase a.f90
> -m32 -mtune=generic -auxbase a -version -I
> /usr/lib/gcc/i386-redhat-linux/4.1.1/finclude -o /tmp/cclnV3Rq.s
>

References:
- 64/32 bit problems..
  - From: Christopher D. Rickett
- Re: 64/32 bit problems..
  - From: FX Coudert

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