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: ICE caused by -O3 and fbounds-check options together

From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
To: Andrew Pinski <pinskia at physics dot uc dot edu>
Cc: Vivek Rao <vivekrao4 at yahoo dot com>, fortran at gcc dot gnu dot org, rguenther at suse dot de
Date: Thu, 12 Oct 2006 15:18:32 -0700
Subject: Re: ICE caused by -O3 and fbounds-check options together
References: <20061012220505.GA11243@troutmask.apl.washington.edu> <200610122218.k9CMIMPt004227@earth.phy.uc.edu>

On Thu, Oct 12, 2006 at 06:18:22PM -0400, Andrew Pinski wrote:
> > 
> > On Thu, Oct 12, 2006 at 02:40:29PM -0700, Vivek Rao wrote:
> > > The program below causes an ICE if compiled with
> > > -fbounds-check and the -O3 option, but not if -O2 or
> > > -O1 are used instead of -O3.
> > > 
> > I cannot reproduce this with
> > GNU Fortran 95 (GCC) 4.2.0 20061009 (experimental)
> > on amd64-*-freebsd.
> 
> Can you also try -m32 -O3 -fbounds-check, that gets
> two cases closer together?
> 

troutmask:sgk[312] gfc4x -m32 -O3 -fbounds-check -c rt.f90
rt.f90: In function 'abc':
rt.f90:5: internal compiler error: in compare_name_with_value, at tree-vrp.c:3561

:(

-- 
Steve

References:
- Re: ICE caused by -O3 and fbounds-check options together
  - From: Steve Kargl
- Re: ICE caused by -O3 and fbounds-check options together
  - From: Andrew Pinski

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