This is the mail archive of the gcc-bugs@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]

[Bug fortran/46205] New: Invalid FORALL fails to compile


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

           Summary: Invalid FORALL fails to compile
           Product: gcc
           Version: 4.5.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: jstottsj@gmail.com


Created attachment 22187
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22187
A very short program that illustrates the problem.

Compiler information:
  Using built-in specs.
  COLLECT_GCC=gfortran
 
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-apple-darwin10.4.0/4.5.1/lto-wrapper
  Target: x86_64-apple-darwin10.4.0
  Configured with: ./configure --enable-languages=c,c++,fortran,lto
  Thread model: posix
  gcc version 4.5.1 (GCC) 

Error message displayed:
  bugtest.f90: In function âforallbugâ:
  bugtest.f90:1: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.

Description:
  An illegal FORALL statement consistently causes the compiler to crash instead
of generating an error message.  To trigger it, pass a vector (of type logical)
as the mask of the FORALL instead of the required scalar logial.

The bug does not depend on the complier flags; "gfortran -c bugtest.f90" is
sufficient.

I've attached a simple program that demonstrates the problem.

-JS


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