[Bug fortran/32236] internal compiler error: in gfc_assign_data_value, at fortran/data.c:288

2007-06-20 Thread burnus at gcc dot gnu dot org


--- Comment #10 from burnus at gcc dot gnu dot org  2007-06-20 20:01 ---
> have tried your suggestion (commenting out the data  
> statement), but the code does not appear to work correctly with this  
> modification.

Try the option -fno-automatic.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32236



[Bug fortran/32236] internal compiler error: in gfc_assign_data_value, at fortran/data.c:288

2007-06-19 Thread pault at gcc dot gnu dot org


--- Comment #9 from pault at gcc dot gnu dot org  2007-06-19 16:44 ---
This is not a regression so no backport.

Paul


-- 

pault at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32236



[Bug fortran/32236] internal compiler error: in gfc_assign_data_value, at fortran/data.c:288

2007-06-19 Thread burnus at gcc dot gnu dot org


--- Comment #8 from burnus at gcc dot gnu dot org  2007-06-19 15:30 ---
Bob,

> Can you please tell me why the compiler flags "tauaero.f:1517" while  
> the problem seems to be associated with the data statement at line  
> 1601?

The line number shown when an internal compiler error occurs is often not
reliably; often something goes wrong at one place, but this is only triggered
when the compiler is at a completely different place. I found the line using
other compilers; but also the brand-new error message of the gfortran 4.3
compiler shows now:

tauaero.f:1601.17:
  data wlbaer/0.,0./
1
tauaero.f:1587.21:
 & wlbaer(2)=0.,
2
Error: 'wlbaer' at (1) already is initialized at (2)

Thus either "=0." in line 1587 or "data wlbaer/0.,0./" needs to be removed.

> I have tried your suggestion (commenting out the data  
> statement), but the code does not appear to work correctly with this  
> modification.

I miss a good test case. If you have one, I'm really interested. However, I
found some divergence in the output compared with other compilers, see PR
32404.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32236



[Bug fortran/32236] internal compiler error: in gfc_assign_data_value, at fortran/data.c:288

2007-06-18 Thread pault at gcc dot gnu dot org


--- Comment #7 from pault at gcc dot gnu dot org  2007-06-18 23:10 ---
Fixed on trunk

Paul


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32236



[Bug fortran/32236] internal compiler error: in gfc_assign_data_value, at fortran/data.c:288

2007-06-18 Thread pault at gcc dot gnu dot org


--- Comment #6 from pault at gcc dot gnu dot org  2007-06-18 23:04 ---
Subject: Bug 32236

Author: pault
Date: Mon Jun 18 23:04:28 2007
New Revision: 125831

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=125831
Log:
2007-06-19  Paul Thomas  <[EMAIL PROTECTED]>

PR fortran/20863
PR fortran/20082
* resolve.c (resolve_code): Use gfc_impure_variable as a
condition for rejecting derived types with pointers, in pure
procedures.
(gfc_impure_variable): Add test for dummy arguments of pure
procedures; any for functions and INTENT_IN for subroutines.

PR fortran/32236
* data.c (gfc_assign_data_value): Change the ICE on an array
reference initializer not being an array into an error and
clear init to prevent a repetition of the error.

2007-06-19  Paul Thomas  <[EMAIL PROTECTED]>

PR fortran/20863
PR fortran/20082
* gfortran.dg/impure_assignment_2.f90 : New test.

PR fortran/32236
* gfortran.dg/data_initialized_2.f90 : New test.

* gfortran.dg/equiv_7.f90 : Test for endianess and call the
appropriate version of 'dmach'.

Added:
trunk/gcc/testsuite/gfortran.dg/data_initialized_2.f90
trunk/gcc/testsuite/gfortran.dg/impure_assignment_2.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/data.c
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/equiv_7.f90


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32236



[Bug fortran/32236] internal compiler error: in gfc_assign_data_value, at fortran/data.c:288

2007-06-17 Thread patchapp at dberlin dot org


--- Comment #5 from patchapp at dberlin dot org  2007-06-17 15:35 ---
Subject: Bug number PR32236

A patch for this bug has been added to the patch tracker.
The mailing list url for the patch is
http://gcc.gnu.org/ml/gcc-patches/2007-06/msg01185.html


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32236



[Bug fortran/32236] internal compiler error: in gfc_assign_data_value, at fortran/data.c:288

2007-06-08 Thread r dot f dot arduini at larc dot nasa dot gov


--- Comment #4 from r dot f dot arduini at larc dot nasa dot gov  
2007-06-08 14:15 ---
Subject: Re:  internal compiler error: in gfc_assign_data_value, at
fortran/data.c:288

Can you please tell me why the compiler flags "tauaero.f:1517" while  
the problem seems to be associated with the data statement at line  
1601?  I have tried your suggestion (commenting out the data  
statement), but the code does not appear to work correctly with this  
modification.

thanks.
Bob


On Jun 6, 2007, at 4:22 PM, burnus at gcc dot gnu dot org wrote:

>
>
> --- Comment #2 from burnus at gcc dot gnu dot org  2007-06-06  
> 20:22 ---
> Your example file misses the "param" module; however, I found it  
> via google:
> http://www.crseo.ucsb.edu/esrg/pauls_dir/sbdart_browser/html_code/ 
> sbdart/params.f.html
>
> The complete package is at:
> ftp://ftp.icess.ucsb.edu/pub/esrg/sbdart/sbdart_2.4.tar.gz
>
> Note: This is a fixed-format Fortran 90 file, not a Fortran 77 file.
>
>  * * *
>
> Using NAG f95 I get the error:
> Error: tauaero.f, line 1601: WLBAER has already been completely  
> initialised
>
> Using g95:
> In file tauaero.f:1601
>   data wlbaer/0.,0./
>1
> Error: Variable 'wlbaer' at (1) already has an initialization
>
> (ifort simply accepts the code.)
>
>
> If one comments out that line 1601, the program actually compiles with
> gfortran.
>
>
> -- 
>
> burnus at gcc dot gnu dot org changed:
>
>What|Removed |Added
> -- 
> --
>  Status|UNCONFIRMED |NEW
>  Ever Confirmed|0   |1
>Keywords||ice-on-invalid-code
>   Known to fail||4.2.0 4.1.3 4.3.0
>Last reconfirmed|-00-00 00:00:00 |2007-06-06 20:22:37
>date||
>Target Milestone|--- |4.3.0
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32236
>
> --- You are receiving this mail because: ---
> You reported the bug, or are watching the reporter.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32236



[Bug fortran/32236] internal compiler error: in gfc_assign_data_value, at fortran/data.c:288

2007-06-06 Thread r dot f dot arduini at larc dot nasa dot gov


--- Comment #3 from r dot f dot arduini at larc dot nasa dot gov  
2007-06-06 21:00 ---
Subject: Re:  internal compiler error: in gfc_assign_data_value, at
fortran/data.c:288

Thank you for your quick and thorough response.  I am now able to  
compile the program with gfortran and can proceed with verifying  
results.

I am new to the Mac OS X and gfortran is what has been installed on  
the machine for me.  Now, I am trying to build confidence in the  
software.

Thanks again for your help.
Bob


On Jun 6, 2007, at 4:22 PM, burnus at gcc dot gnu dot org wrote:

>
>
> --- Comment #2 from burnus at gcc dot gnu dot org  2007-06-06  
> 20:22 ---
> Your example file misses the "param" module; however, I found it  
> via google:
> http://www.crseo.ucsb.edu/esrg/pauls_dir/sbdart_browser/html_code/ 
> sbdart/params.f.html
>
> The complete package is at:
> ftp://ftp.icess.ucsb.edu/pub/esrg/sbdart/sbdart_2.4.tar.gz
>
> Note: This is a fixed-format Fortran 90 file, not a Fortran 77 file.
>
>  * * *
>
> Using NAG f95 I get the error:
> Error: tauaero.f, line 1601: WLBAER has already been completely  
> initialised
>
> Using g95:
> In file tauaero.f:1601
>   data wlbaer/0.,0./
>1
> Error: Variable 'wlbaer' at (1) already has an initialization
>
> (ifort simply accepts the code.)
>
>
> If one comments out that line 1601, the program actually compiles with
> gfortran.
>
>
> -- 
>
> burnus at gcc dot gnu dot org changed:
>
>What|Removed |Added
> -- 
> --
>  Status|UNCONFIRMED |NEW
>  Ever Confirmed|0   |1
>Keywords||ice-on-invalid-code
>   Known to fail||4.2.0 4.1.3 4.3.0
>Last reconfirmed|-00-00 00:00:00 |2007-06-06 20:22:37
>date||
>Target Milestone|--- |4.3.0
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32236
>
> --- You are receiving this mail because: ---
> You reported the bug, or are watching the reporter.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32236



[Bug fortran/32236] internal compiler error: in gfc_assign_data_value, at fortran/data.c:288

2007-06-06 Thread burnus at gcc dot gnu dot org


--- Comment #2 from burnus at gcc dot gnu dot org  2007-06-06 20:22 ---
Your example file misses the "param" module; however, I found it via google:
http://www.crseo.ucsb.edu/esrg/pauls_dir/sbdart_browser/html_code/sbdart/params.f.html

The complete package is at:
ftp://ftp.icess.ucsb.edu/pub/esrg/sbdart/sbdart_2.4.tar.gz

Note: This is a fixed-format Fortran 90 file, not a Fortran 77 file.

 * * *

Using NAG f95 I get the error:
Error: tauaero.f, line 1601: WLBAER has already been completely initialised

Using g95:
In file tauaero.f:1601
  data wlbaer/0.,0./
   1
Error: Variable 'wlbaer' at (1) already has an initialization

(ifort simply accepts the code.)


If one comments out that line 1601, the program actually compiles with
gfortran.


-- 

burnus at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1
   Keywords||ice-on-invalid-code
  Known to fail||4.2.0 4.1.3 4.3.0
   Last reconfirmed|-00-00 00:00:00 |2007-06-06 20:22:37
   date||
   Target Milestone|--- |4.3.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32236



[Bug fortran/32236] internal compiler error: in gfc_assign_data_value, at fortran/data.c:288

2007-06-06 Thread r dot f dot arduini at larc dot nasa dot gov


--- Comment #1 from r dot f dot arduini at larc dot nasa dot gov  
2007-06-06 18:41 ---
Created an attachment (id=13661)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13661&action=view)
part of fortran 77 package


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32236