public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos.a.cruz at nasa dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60529] New: internal compiler error with allocatable sub-component
Date: Fri, 14 Mar 2014 17:55:00 -0000 [thread overview]
Message-ID: <bug-60529-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60529
Bug ID: 60529
Summary: internal compiler error with allocatable sub-component
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: carlos.a.cruz at nasa dot gov
Using the following compiler release:
GNU Fortran (GCC) 4.9.0 20140309 (experimental)
on the following reproducer:
---
module T_mod
implicit none
type :: TS
integer, allocatable :: i(:)
end type TS
type :: T
! The following line causes an internal compiler error.
type (TS) :: s(1)
! The following line does not:
! type (TS), allocatable :: s(:)
end type T
contains
subroutine insert(this)
class(T) :: this
end subroutine insert
end module T_mod
---
yields an internal compiler error:
repro.F90: In function ‘__final_t_mod_T’:
repro.F90:19:0: internal compiler error: in gfc_conv_descriptor_data_get, at
fortran/trans-array.c:145
end module T_mod
^
0x511048 ???
../sysdeps/x86_64/elf/start.S:113
I am running on a Linux cluster:
Linux discover28 2.6.32.54-0.3-default #1 SMP 2012-01-27 17:38:56 +0100 x86_64
x86_64 x86_64 GNU/Linux
Note that the internal compiler error does not occur with two earlier releases
of gfortran:
GNU Fortran (GCC) 4.9.0 20140105 (experimental)
GNU Fortran (GCC) 4.8.1
>From gcc-bugs-return-446316-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Mar 14 17:59:30 2014
Return-Path: <gcc-bugs-return-446316-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25325 invoked by alias); 14 Mar 2014 17:59:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25027 invoked by uid 55); 14 Mar 2014 17:59:25 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/60484] [4.7/4.8/4.9 Regression] -fdump-rtl-expand and attribute optimize gives incorrect dump file path
Date: Fri, 14 Mar 2014 17:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60484-4-RaHrMdueLu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60484-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60484-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-03/txt/msg01185.txt.bz2
Content-length: 563
http://gcc.gnu.org/bugzilla/show_bug.cgi?id`484
--- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Fri Mar 14 17:58:52 2014
New Revision: 208571
URL: http://gcc.gnu.org/viewcvs?rev 8571&root=gcc&view=rev
Log:
PR middle-end/60484
* common.opt (dump_base_name_prefixed): New Variable.
* opts.c (finish_options): Don't prepend directory to x_dump_base_name
if x_dump_base_name_prefixed is already set, set it at the end.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/common.opt
trunk/gcc/opts.c
next reply other threads:[~2014-03-14 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 17:55 carlos.a.cruz at nasa dot gov [this message]
2014-03-15 10:35 ` [Bug fortran/60529] [4.9 Regression] [OOP] ICE " janus at gcc dot gnu.org
2014-03-15 10:56 ` dominiq at lps dot ens.fr
2014-03-31 8:55 ` rguenth at gcc dot gnu.org
2014-03-31 9:44 ` rguenth at gcc dot gnu.org
2014-04-22 11:35 ` [Bug fortran/60529] [4.9/4.10 " jakub at gcc dot gnu.org
2014-07-16 13:27 ` jakub at gcc dot gnu.org
2014-07-17 17:20 ` dominiq at lps dot ens.fr
2015-02-08 15:42 ` pault at gcc dot gnu.org
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-60529-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).