[Bug fortran/37039] Cray pointer with pointee DIMENSION statement after POINTER statement

2010-05-12 Thread langton at gcc dot gnu dot org 


--- Comment #3 from langton at gcc dot gnu dot org  2010-05-12 15:57 ---
I don't think this is a dupe of either of those bugs.  In this case, the
dimension attribute isn't properly applied to 'tab' on line 5.  The problem
appears to be in variable_decl() (decl.c), where I kept an extra gfc_array_spec
(cp_as) that isn't merged with current_as.  I'm trying to recall why cp_as was
necessary, and whether it's still necessary.


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||langton2 at llnl dot gov


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

[Bug fortran/37039] Cray pointer with pointee DIMENSION statement after POINTER statement

2010-05-12 Thread langton at gcc dot gnu dot org 


--- Comment #4 from langton at gcc dot gnu dot org  2010-05-12 16:51 ---
Created an attachment (id=20651)
 -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20651action=view)
Possible fix (minimal testing)

Removing cp_as entirely seems to work.  I'll have to test this some more.


-- 


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

[Bug fortran/37039] Cray pointer with pointee DIMENSION statement after POINTER statement

2010-05-12 Thread langton at gcc dot gnu dot org 


--- Comment #5 from langton at gcc dot gnu dot org  2010-05-12 19:37 ---
The patch I posted isn't correct.  It causes a regression in
gfortran.dg/cray_pointers_2.f90.


-- 


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

[Bug fortran/37039] Cray pointer with pointee DIMENSION statement after POINTER statement

2010-05-12 Thread langton at gcc dot gnu dot org 


--- Comment #6 from langton at gcc dot gnu dot org  2010-05-12 22:14 ---
Created an attachment (id=20653)
 -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20653action=view)
decl.c patch

Trying again: this patch fixes the bug in the testcase and passes regression
testing.


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

  Attachment #20651|0   |1
is obsolete||


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

[Bug fortran/43985] New: ICE when assumed size cray-pointee passed as argument

2010-05-04 Thread langton at gcc dot gnu dot org 
The recent fix for PR fortran/43331 introduced a regression for programs that
use OpenMP and pass assumed-size cray-pointees as function arguments.  Here is
an example:

 subroutine bob()
 implicit none
 real(8) peted
 pointer (ipeted, peted(*))
 integer(4) sz
!$omp parallel default(shared)

 call pete(peted(sz))

!$omp end parallel
 return
 end subroutine bob


When compiled with svn revision = 157512, this generates an ICE:

% gfortran -fcray-pointer -fopenmp -c bug1.f90
bug1.f90: In function 'bob':
bug1.f90:9:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html for instructions.

My guess is that this is a result of 'peted' have the AS_ASSUMED_SIZE attribute
instead of AS_EXPLICIT in trans-decl.c


-- 
   Summary: ICE when assumed size cray-pointee passed as argument
   Product: gcc
   Version: 4.5.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: langton at gcc dot gnu dot org
ReportedBy: langton at gcc dot gnu dot org


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

[Bug fortran/37039] Cray pointer with pointee DIMENSION statement after POINTER statement

2010-02-10 Thread langton at gcc dot gnu dot org 


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |langton at gcc dot gnu dot
   |dot org |org
 Status|NEW |ASSIGNED
   Last reconfirmed|2009-03-29 08:26:51 |2010-02-10 19:38:57
   date||


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

[Bug fortran/33526] FAIL: gfortran.dg/openmp_stack.f90 -O0 (test for excess errors)

2007-09-22 Thread langton at gcc dot gnu dot org 


--- Comment #2 from langton at gcc dot gnu dot org  2007-09-22 14:17 ---
Okay, sorry about that!

I'll ping Jakub Jelinek for approval to move this into
libgomp/testsuite/libgomp.fortran.


-- 


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

[Bug fortran/20441] -finit-local-zero is missing from gfortran

2007-09-20 Thread langton at gcc dot gnu dot org 


--- Comment #11 from langton at gcc dot gnu dot org  2007-09-21 02:34 
---
Subject: Bug 20441

Author: langton
Date: Fri Sep 21 02:34:14 2007
New Revision: 128643

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=128643
Log:
PR fortran/20441
* gfortran.h : Add init_local_* enums and init_flag_* flags to
gfc_option_t.
* lang.opt: Add -finit-local-zero, -finit-real, -finit-integer,
-finit-character, and -finit-logical flags.
* invoke.texi: Document new options.
* resolve.c (build_init_assign): New function.
(apply_init_assign): Move part of function into build_init_assign.
(build_default_init_expr): Build local initializer (-finit-*).
(apply_default_init_local): Apply local initializer (-finit-*).
(resolve_fl_variable): Try to add local initializer (-finit-*).
* options.c (gfc_init_options, gfc_handle_option,
gfc_post_options): Handle -finit-local-zero, -finit-real,
-finit-integer, -finit-character, and -finit-logical flags.

PR fortran/20441
* gfortran.dg/init_flag_1.f90: New.
* gfortran.dg/init_flag_2.f90: New.
* gfortran.dg/init_flag_3.f90: New.
* gfortran.dg/init_flag_4.f90: New.
* gfortran.dg/init_flag_5.f90: New.
* gfortran.dg/init_flag_6.f90: New.
* gfortran.dg/init_flag_7.f90: New.


Added:
trunk/gcc/testsuite/gfortran.dg/init_flag_1.f90
trunk/gcc/testsuite/gfortran.dg/init_flag_2.f90
trunk/gcc/testsuite/gfortran.dg/init_flag_3.f90
trunk/gcc/testsuite/gfortran.dg/init_flag_4.f90
trunk/gcc/testsuite/gfortran.dg/init_flag_5.f90
trunk/gcc/testsuite/gfortran.dg/init_flag_6.f90
trunk/gcc/testsuite/gfortran.dg/init_flag_7.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/gfortran.h
trunk/gcc/fortran/invoke.texi
trunk/gcc/fortran/lang.opt
trunk/gcc/fortran/options.c
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog


-- 


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

[Bug fortran/20441] -finit-local-zero is missing from gfortran

2007-09-20 Thread langton at gcc dot gnu dot org 


--- Comment #12 from langton at gcc dot gnu dot org  2007-09-21 02:40 
---
Fixed on trunk as of revision 128643.


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution||FIXED


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

[Bug fortran/20441] -finit-local-zero is missing from gfortran

2007-08-20 Thread langton at gcc dot gnu dot org 


--- Comment #10 from langton at gcc dot gnu dot org  2007-08-20 15:07 
---
(In reply to comment #9)
 Adding -finit-real=nan (http://gcc.gnu.org/ml/fortran/2007-08/msg00408.html) 
 is
 a real bonus for gfortran. 
 Any chance to add -finit-real=snan to set Signalling NaN ?
 A SNaN cannot be the result of any arithmetic operations, hence a good choice
 for a unset pattern. The NAG compiler uses SNaN when using -nan.

I'd like to add finit-real=snan.  Right now, this requires a bit of a hack,
since mpfr (which we use internally for real constants) doesn't distinguish
between signaling and quiet NaNs:

http://gcc.gnu.org/ml/fortran/2007-07/msg00512.html
http://websympa.loria.fr/wwsympa/arc/mpfr/2007-07/msg00118.html


-- 


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

[Bug fortran/32703] ICE with [trim(character_variable)]

2007-07-09 Thread langton at gcc dot gnu dot org 


--- Comment #1 from langton at gcc dot gnu dot org  2007-07-09 18:32 ---
Confirmed.  The segfault occurs on trans-array.c:1380 because e-ts-cl is
null.


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1
   Last reconfirmed|-00-00 00:00:00 |2007-07-09 18:32:53
   date||


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

[Bug fortran/20441] -finit-local-zero is missing from gfortran

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


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |langton at gcc dot gnu dot
   |dot org |org
 Status|NEW |ASSIGNED
   Last reconfirmed|2005-12-18 01:54:45 |2007-06-18 16:23:28
   date||


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

[Bug tree-optimization/28411] Illegal instruction error with -ftrapv

2006-07-18 Thread langton at gcc dot gnu dot org 


--- Comment #7 from langton at gcc dot gnu dot org  2006-07-18 16:30 ---
(In reply to comment #4)
 This is the backtrace for the testcase in comment #3:

I didn't post the Linux output for the C testcase, but I was seeing either
segmentation faults after a long wait or (occasionally) virtual memory
exhausted errors, instead of the explicit fold-const ICE that resulted on an
Intel Mac.


-- 


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

[Bug fortran/28411] gfortran: Internal error: Illegal instruction

2006-07-17 Thread langton at gcc dot gnu dot org 


--- Comment #1 from langton at gcc dot gnu dot org  2006-07-17 21:42 ---
I can confirm that there is a problem here, but I am getting different output. 
On MacIntel:

york.llnl.gov(771)% gfortran -c -O2 -mfpmath=sse -msse -msse2
-ffpe-trap=invalid,zero,overflow -ftrapping-math -ftrapv -fmath-errno
module_utilities2.f90
module_utilities2.f90: In function 'test_check_sums':
module_utilities2.f90:16: internal compiler error: in fold_binary, at
fold-const.c:8250
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://gcc.gnu.org/bugs.html for instructions.
york.llnl.gov(772)% gfortran --v   
Using built-in specs.
Target: i686-apple-darwin8
Configured with: ../../source/gcc_source/configure --prefix=/home/langton2/opt
--with-gmp=/home/langton2/opt --with-mpfr=/home/langton2/opt
--enable-languages=c,fortran --with-arch=pentium-m --with-tune=prescott
--target=i686-apple-darwin8 --host=i686-apple-darwin8
--build=i686-apple-darwin8
Thread model: posix
gcc version 4.2.0 20060617 (experimental)

On i686-pc-linux:
ilx1(1052)% gfortran -c -O2 -mfpmath=sse -msse -msse2
-ffpe-trap=invalid,zero,overflow -ftrapping-math -ftrapv -fmath-errno
module_utilities2.f90
module_utilities2.f90: In function 'test_check_sums':
module_utilities2.f90:16: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://gcc.gnu.org/bugs.html for instructions.
ilx1(1053)% gfortran --v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../../../mainline_source/configure
--prefix=/usr/gapps/opnsrc/langton2/chaos_3_x86/mainline
--with-gmp=/usr/gapps/opnsrc/langton2/chaos_3_x86/mainline
--with-mpfr=/usr/gapps/opnsrc/langton2/chaos_3_x86/mainline
--enable-languages=c,c++,java,fortran
Thread model: posix
gcc version 4.2.0 20060613 (experimental)

I can't get a  complete core dump on either platform.  On the Mac, I see:

york.llnl.gov(773)% gfortran -c -O2 -mfpmath=sse -msse -msse2
-ffpe-trap=invalid,zero,overflow -ftrapping-math -ftrapv -fmath-errno -dH
module_utilities2.f90
module_utilities2.f90: In function 'test_check_sums':
module_utilities2.f90:16: internal compiler error: in fold_binary, at
fold-const.c:8250
gfortran: Internal error: Abort trap (program f951)
Please submit a full bug report.
See URL:http://gcc.gnu.org/bugs.html for instructions.

On Linux, adding -dH causes the command to hang, and when I killed the command,
the resulting incomplete core file was greater that 2GB.


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||langton at gcc dot gnu dot
   ||org
 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1
   Last reconfirmed|-00-00 00:00:00 |2006-07-17 21:42:32
   date||


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

[Bug fortran/28411] gfortran: Internal error: Illegal instruction

2006-07-17 Thread langton at gcc dot gnu dot org 


--- Comment #2 from langton at gcc dot gnu dot org  2006-07-17 21:57 ---
The flags -O2 -ftrapv are sufficient to reproduce this crash.  I get the same
result on the Mac, and on Linux:

ilx1(1067)% gfortran -c -O2 -ftrapv module_utilities2.f90
virtual memory exhausted: Cannot allocate memory


-- 


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

[Bug middle-end/28411] gfortran: Internal error: Illegal instruction

2006-07-17 Thread langton at gcc dot gnu dot org 


--- Comment #3 from langton at gcc dot gnu dot org  2006-07-17 22:26 ---
This doesn't appear to be a gfortran bug.  On both i686-darwin and
i686-pc-linux, a comparable C program crashes in the same way:

york.llnl.gov(831)% cat foo.c 
void test_check_sums()
{
  const int SIZE = 10;
  int array_i4[SIZE];
  long long array_i8[SIZE];
  double array_r8[SIZE];
  float array_r4[SIZE];
  int n;

for (n = 0; n SIZE; n++)
  {
array_i4[n] = (int) -3*n;
array_i8[n] = (long long) -3*n;
array_r4[n] = (float) -3*n;
array_r8[n] = (double) -3*n;
  }

}
york.llnl.gov(832)% gcc -ftrapv -c -O2 foo.c
foo.c: In function 'test_check_sums':
foo.c:2: internal compiler error: in fold_binary, at fold-const.c:8239
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://gcc.gnu.org/bugs.html for instructions.
york.llnl.gov(833)% gcc -v
Using built-in specs.
Target: i386-apple-darwin8.7.1
Configured with: ../../source/mainline_source/configure
--prefix=/home/langton2/opt_mactel/ --with-gmp=/home/langton2/opt_mactel/
--with-mpfr=/home/langton2/opt_mactel/ --enable-languages=c,fortran
Thread model: posix
gcc version 4.2.0 20060703 (experimental)


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

  Component|fortran |middle-end


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

[Bug libfortran/26893] kinds.h not generated, causing failure

2006-07-13 Thread langton at gcc dot gnu dot org 


--- Comment #17 from langton at gcc dot gnu dot org  2006-07-13 21:00 
---
(In reply to comment #16)
 
 Thanks but it doesn't work...

Did you re-run 'configure' after rebuilding GMP and MPFR?  What happens if you
try to configure and bootstrap from a clean object directory?


-- 


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

[Bug other/28297] GCC 4.1.1 fails to build on Mac OS X 10.4.6

2006-07-13 Thread langton at gcc dot gnu dot org 


--- Comment #8 from langton at gcc dot gnu dot org  2006-07-13 21:11 ---
(In reply to comment #0)
 3. Run ./configure --enable-threads --x-includes=/usr/X11R6
 --x-libraries=/usr/X11R6 --with-cpu=powerpc --with-mpfr=/usr/local/lib
 --with-gmp=/usr/local/lib.


Are you building in the source directory?  If so, try creating a new object
directory, then 'configure' and 'make bootstrap' from that directory.


-- 


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

[Bug fortran/24748] substring of implicitly typed variable not rejected

2006-06-30 Thread langton at gcc dot gnu dot org 


--- Comment #5 from langton at gcc dot gnu dot org  2006-06-30 16:41 ---
Subject: Bug 24748

Author: langton
Date: Fri Jun 30 16:41:11 2006
New Revision: 115092

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=115092
Log:
PR fortran/24748
* gfortran.dg/implicit_8.f90: New.

PR fortran/24748
* primary.c (gfc_match_rvalue): Don't call
match_substring for implicit non-character types.

Added:
branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/implicit_8.f90
  - copied unchanged from r114901,
trunk/gcc/testsuite/gfortran.dg/implicit_8.f90
Modified:
branches/gcc-4_1-branch/gcc/fortran/ChangeLog
branches/gcc-4_1-branch/gcc/fortran/primary.c
branches/gcc-4_1-branch/gcc/testsuite/ChangeLog


-- 


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

[Bug target/25765] gfortran.dg/assign_2.f90 -O0 fails

2006-06-30 Thread langton at gcc dot gnu dot org 


--- Comment #6 from langton at gcc dot gnu dot org  2006-06-30 16:46 ---
This is fixed in 4.2 as of revision 115079.  I'll backport the fix to 4.1 in
the next few days:

http://gcc.gnu.org/ml/gcc-patches/2006-06/msg01492.html


-- 


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

[Bug fortran/24748] substring of implicitly typed variable not rejected

2006-06-30 Thread langton at gcc dot gnu dot org 


--- Comment #6 from langton at gcc dot gnu dot org  2006-06-30 16:48 ---
Fix backported to 4.1.


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution||FIXED


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

[Bug target/25765] gfortran.dg/assign_2.f90 -O0 fails

2006-06-27 Thread langton at gcc dot gnu dot org 


--- Comment #4 from langton at gcc dot gnu dot org  2006-06-27 20:13 ---
The rs6000 patch (attached) does appear to work, at least on assign_2.f90. 
I'll do a full bootstrap and regression-test, then submit the fix.


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||langton at gcc dot gnu dot
   ||org
 AssignedTo|unassigned at gcc dot gnu   |langton at gcc dot gnu dot
   |dot org |org
 Status|NEW |ASSIGNED


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

[Bug target/25765] gfortran.dg/assign_2.f90 -O0 fails

2006-06-27 Thread langton at gcc dot gnu dot org 


--- Comment #5 from langton at gcc dot gnu dot org  2006-06-27 20:15 ---
Created an attachment (id=11761)
 -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11761action=view)
Geoffrey Keating's rs6000 patch applied to i386.


-- 


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

[Bug fortran/24748] substring of implicitly typed variable not rejected

2006-06-22 Thread langton at gcc dot gnu dot org 


--- Comment #3 from langton at gcc dot gnu dot org  2006-06-22 18:30 ---
Subject: Bug 24748

Author: langton
Date: Thu Jun 22 18:30:18 2006
New Revision: 114901

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=114901
Log:
PR fortran/24748
* primary.c (gfc_match_rvalue): Don't call match_substring for
implicit non-character types.

PR fortran/24748
* gfortran.dg/implicit_8.f90: New.


Added:
trunk/gcc/testsuite/gfortran.dg/implicit_8.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/primary.c
trunk/gcc/testsuite/ChangeLog


-- 


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

[Bug fortran/24748] substring of implicitly typed variable not rejected

2006-06-22 Thread langton at gcc dot gnu dot org 


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |langton at gcc dot gnu dot
   |dot org |org
 Status|NEW |ASSIGNED


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

[Bug fortran/24748] substring of implicitly typed variable not rejected

2006-06-21 Thread langton at gcc dot gnu dot org 


--- Comment #2 from langton at gcc dot gnu dot org  2006-06-21 23:40 ---
Here's a proposed fix:

http://gcc.gnu.org/ml/gcc-patches/2006-06/msg01216.html


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||langton at gcc dot gnu dot
   ||org


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

[Bug libfortran/26893] kinds.h not generated, causing failure

2006-06-20 Thread langton at gcc dot gnu dot org 


--- Comment #15 from langton at gcc dot gnu dot org  2006-06-20 23:32 
---
(In reply to comment #14)
 GMP-4.2
 ./configure --prefix=/opt --with-gnu-ld --disable-cxx  --disable-nails 
 --disable-mpfr
 MPFR-2.2
 ./configure --enable-mpfr --with-gmp-=/opt --prefix=/opt --with-gmp-lib=/opt
 --with-gmp-include=/opt  make -j2
 
 I think that both libraries are 32 bits libraries, not 64.
 
 GCC
 ../configure --prefix=/opt --enable-threads=posix
 --enable-languages=c,c++,fortran,java --with-gnu-as --with-gnu-ld
 --with-mpfr=/opt --disable-multilib  make -j2 bootstrap
 

Try adding ABI=32 to the GMP options.  I don't have a SPARC box, but on
AIX-ppc, this was necessary to force GMP to build a 32-bit library.  See also:

http://www.swox.com/gmp/manual/ABI-and-ISA.html#ABI-and-ISA


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||langton at gcc dot gnu dot
   ||org


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

[Bug fortran/27786] [4.1 only] Bad interaction between Cray pointer, assumed-size array and bounds checking

2006-06-15 Thread langton at gcc dot gnu dot org 


--- Comment #6 from langton at gcc dot gnu dot org  2006-06-15 23:07 ---
Subject: Bug 27786

Author: langton
Date: Thu Jun 15 23:07:14 2006
New Revision: 114692

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=114692
Log:
PR fortran/27786
* cray_pointers_2.f90: Add -fbounds-check compile flag.

PR fortran/27786
* trans-array.c (gfc_conv_array_ref): Eliminate bounds checking
for assumed-size Cray pointees.


Modified:
branches/gcc-4_1-branch/gcc/fortran/ChangeLog
branches/gcc-4_1-branch/gcc/fortran/trans-array.c
branches/gcc-4_1-branch/gcc/testsuite/ChangeLog
branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/cray_pointers_2.f90


-- 


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

[Bug fortran/27786] [4.1 only] Bad interaction between Cray pointer, assumed-size array and bounds checking

2006-06-15 Thread langton at gcc dot gnu dot org 


--- Comment #7 from langton at gcc dot gnu dot org  2006-06-15 23:11 ---
I've backported the patch to 4.1, so this bug should be resolved.


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||FIXED


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

[Bug fortran/27786] Bad interaction between Cray pointer, assumed-size array and bounds checking

2006-06-08 Thread langton at gcc dot gnu dot org 


--- Comment #3 from langton at gcc dot gnu dot org  2006-06-08 21:01 ---
Subject: Bug 27786

Author: langton
Date: Thu Jun  8 21:00:26 2006
New Revision: 114495

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=114495
Log:
* cray_pointers_2.f90: Add -fbounds-check compile flag.

PR fortran/27786
* trans-array.c (gfc_conv_array_ref): Eliminate bounds checking
for assumed-size Cray pointees.


Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-array.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/cray_pointers_2.f90


-- 


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

[Bug fortran/27786] Bad interaction between Cray pointer, assumed-size array and bounds checking

2006-06-08 Thread langton at gcc dot gnu dot org 


--- Comment #4 from langton at gcc dot gnu dot org  2006-06-08 21:03 ---
I've committed a patch that should fix this bug.


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution||FIXED


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

[Bug fortran/27786] Bad interaction between Cray pointer, assumed-size array and bounds checking

2006-06-06 Thread langton at gcc dot gnu dot org 


-- 

langton at gcc dot gnu dot org changed:

   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |langton at gcc dot gnu dot
   |dot org |org
 Status|NEW |ASSIGNED


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