public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "longb at cray dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/55501] New: ICE using MERGE in constant expr Date: Wed, 28 Nov 2012 00:27:00 -0000 [thread overview] Message-ID: <bug-55501-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55501 Bug #: 55501 Summary: ICE using MERGE in constant expr Classification: Unclassified Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: longb@cray.com Test (extracted from a larger module) > cat test2.f90 module test integer,parameter,private :: int32 = 4 integer,private,parameter :: dik = kind(0) ! Default Integer Kind type MPI_Datatype integer :: mpi_val end type type(MPI_Datatype),parameter,private :: MPIx_I4 = MPI_Datatype(4) type(MPI_Datatype),parameter,private :: MPIx_I8 = MPI_Datatype(8) type(MPI_Datatype),parameter :: MPI_INTEGER = merge(MPIx_I4, MPIx_I8, dik==int32) end module test > ftn -c test2.f90 f951: internal compiler error: in gfc_conv_structure, at fortran/trans-expr.c:5360 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Also fails with 4.8. Allowing MERGE here is a F2003 feature (elemental intrinsic with constant arguments). In any case, the compiler should not abort. Compiles OK with Cray compiler.
next reply other threads:[~2012-11-28 0:27 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-28 0:27 longb at cray dot com [this message] 2012-11-28 0:37 ` [Bug fortran/55501] " longb at cray dot com 2012-11-28 9:16 ` [Bug fortran/55501] [F03] " janus at gcc dot gnu.org 2012-11-28 9:40 ` janus at gcc dot gnu.org 2012-11-28 10:11 ` janus at gcc dot gnu.org 2012-11-28 10:36 ` janus at gcc dot gnu.org 2012-11-28 10:49 ` burnus at gcc dot gnu.org 2012-11-28 10:50 ` janus at gcc dot gnu.org 2012-11-28 10:55 ` burnus at gcc dot gnu.org 2012-11-28 11:04 ` burnus at gcc dot gnu.org 2012-11-28 12:17 ` janus at gcc dot gnu.org 2012-11-28 12:22 ` janus at gcc dot gnu.org 2012-11-28 14:54 ` burnus at gcc dot gnu.org 2013-09-26 4:43 ` longb at cray dot com
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-55501-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: linkBe 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).