public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Bader at lrz dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57117] New: ICE for sourced allocation of a UP entity that uses the transpose intrinsic
Date: Mon, 29 Apr 2013 19:59:00 -0000	[thread overview]
Message-ID: <bug-57117-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 57117
           Summary: ICE for sourced allocation of a UP entity that uses
                    the transpose intrinsic
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: Bader@lrz.de


Created attachment 29977
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29977
module and main program as standalone source.

The attached source code causes a segfault in gfortran at compile time: 

intrinsics_02_pos.f90:61:0: internal compiler error: Segmentation fault
   allocate(y(3,3), source=transpose(x))
0x87e07f crash_signal             
        ../../gcc-4.8.0/gcc/toplev.c:332
0x5ad22b gfc_conv_scalarized_array_ref
        ../../gcc-4.8.0/gcc/fortran/trans-array.c:3037
0x5adb89 gfc_conv_array_ref(gfc_se*, gfc_array_ref*, gfc_symbol*, locus*)
        ../../gcc-4.8.0/gcc/fortran/trans-array.c:3172
0x5d0cdf gfc_conv_variable
        ../../gcc-4.8.0/gcc/fortran/trans-expr.c:1809
0x5cddaa gfc_conv_expr(gfc_se*, gfc_expr*)
        ../../gcc-4.8.0/gcc/fortran/trans-expr.c:6266
0x5e158c gfc_conv_intrinsic_function(gfc_se*, gfc_expr*)
        ../../gcc-4.8.0/gcc/fortran/trans-intrinsic.c:6697
0x5cd832 gfc_conv_function_expr
        ../../gcc-4.8.0/gcc/fortran/trans-expr.c:5547
0x5cdd1a gfc_conv_expr(gfc_se*, gfc_expr*)
        ../../gcc-4.8.0/gcc/fortran/trans-expr.c:6258
0x5d1d05 gfc_conv_expr_reference(gfc_se*, gfc_expr*)
        ../../gcc-4.8.0/gcc/fortran/trans-expr.c:6387
0x5f30be gfc_trans_allocate(gfc_code*)
        ../../gcc-4.8.0/gcc/fortran/trans-stmt.c:4911
0x5a7647 trans_code
        ../../gcc-4.8.0/gcc/fortran/trans.c:1577
0x5c4be2 gfc_generate_function_code(gfc_namespace*)
        ../../gcc-4.8.0/gcc/fortran/trans-decl.c:5397
0x568880 translate_all_program_units
        ../../gcc-4.8.0/gcc/fortran/parse.c:4468
0x568880 gfc_parse_file()
        ../../gcc-4.8.0/gcc/fortran/parse.c:4682
0x5a3c25 gfc_be_parse_file
        ../../gcc-4.8.0/gcc/fortran/f95-lang.c:189


             reply	other threads:[~2013-04-29 19:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-29 19:59 Bader at lrz dot de [this message]
2013-04-29 21:34 ` [Bug fortran/57117] " dominiq at lps dot ens.fr
2013-04-30 12:22 ` [Bug fortran/57117] [OOP] ICE for sourced allocation of a polymorphic entity using TRANSPOSE janus at gcc dot gnu.org
2015-10-25 15:54 ` pault at gcc dot gnu.org
2015-10-28 14:58 ` pault at gcc dot gnu.org
2015-10-28 17:24 ` dominiq at lps dot ens.fr
2015-10-29 12:33 ` dominiq at lps dot ens.fr
2015-10-29 19:02 ` pault at gcc dot gnu.org
2015-10-30  8:38 ` dominiq at lps dot ens.fr
2015-10-30  9:29 ` paul.richard.thomas at gmail dot com
2015-10-30  9:39 ` dominiq at lps dot ens.fr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-57117-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).