public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matthew.hambley at metoffice dot gov.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/63230] allocation of deferred length character as derived type component causes internal compiler error Date: Fri, 21 Nov 2014 12:25:00 -0000 [thread overview] Message-ID: <bug-63230-4-Ws3sQNlvQC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63230-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63230 --- Comment #3 from matthew.hambley at metoffice dot gov.uk --- (In reply to matthew.hambley from comment #2) > Created attachment 34067 [details] > Minimal test case for the issue under v4.9.2. > > I just stumbled across this in v4.9.2. Attached is a minimal test case. And I should have included the compiler output: $ gfortran -Wall -Wextra stringalloc.f90 stringalloc.f90: In function ‘test’: stringalloc.f90:20:0: internal compiler error: in gimplify_expr, at gimplify.c:8538 allocate( character( len=len_trim( thing ) ) :: local%thing ) ^ 0x80569e gimplify_expr(tree_node**, gimple_statement_base**, gimple_statement_base**, bool (*)(tree_node*), int) ../../gcc-4.9.2/gcc/gimplify.c:8538 0x802929 gimplify_modify_expr ../../gcc-4.9.2/gcc/gimplify.c:4510 0x804b67 gimplify_expr(tree_node**, gimple_statement_base**, gimple_statement_base**, bool (*)(tree_node*), int) ../../gcc-4.9.2/gcc/gimplify.c:7627 0x806586 gimplify_stmt(tree_node**, gimple_statement_base**) ../../gcc-4.9.2/gcc/gimplify.c:5373 0x805033 gimplify_statement_list ../../gcc-4.9.2/gcc/gimplify.c:1432 0x805033 gimplify_expr(tree_node**, gimple_statement_base**, gimple_statement_base**, bool (*)(tree_node*), int) ../../gcc-4.9.2/gcc/gimplify.c:8042 0x806586 gimplify_stmt(tree_node**, gimple_statement_base**) ../../gcc-4.9.2/gcc/gimplify.c:5373 0x806e1b gimplify_bind_expr ../../gcc-4.9.2/gcc/gimplify.c:1099 0x80438e gimplify_expr(tree_node**, gimple_statement_base**, gimple_statement_base**, bool (*)(tree_node*), int) ../../gcc-4.9.2/gcc/gimplify.c:7824 0x806586 gimplify_stmt(tree_node**, gimple_statement_base**) ../../gcc-4.9.2/gcc/gimplify.c:5373 0x805033 gimplify_statement_list ../../gcc-4.9.2/gcc/gimplify.c:1432 0x805033 gimplify_expr(tree_node**, gimple_statement_base**, gimple_statement_base**, bool (*)(tree_node*), int) ../../gcc-4.9.2/gcc/gimplify.c:8042 0x806586 gimplify_stmt(tree_node**, gimple_statement_base**) ../../gcc-4.9.2/gcc/gimplify.c:5373 0x80408a gimplify_and_add ../../gcc-4.9.2/gcc/gimplify.c:385 0x80408a gimplify_expr(tree_node**, gimple_statement_base**, gimple_statement_base**, bool (*)(tree_node*), int) ../../gcc-4.9.2/gcc/gimplify.c:7964 0x806586 gimplify_stmt(tree_node**, gimple_statement_base**) ../../gcc-4.9.2/gcc/gimplify.c:5373 0x806e1b gimplify_bind_expr ../../gcc-4.9.2/gcc/gimplify.c:1099 0x80438e gimplify_expr(tree_node**, gimple_statement_base**, gimple_statement_base**, bool (*)(tree_node*), int) ../../gcc-4.9.2/gcc/gimplify.c:7824 0x806586 gimplify_stmt(tree_node**, gimple_statement_base**) ../../gcc-4.9.2/gcc/gimplify.c:5373 0x80743a gimplify_body(tree_node*, bool) ../../gcc-4.9.2/gcc/gimplify.c:8734 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions. >From gcc-bugs-return-467934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 21 12:38:04 2014 Return-Path: <gcc-bugs-return-467934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 9414 invoked by alias); 21 Nov 2014 12:38:04 -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 8963 invoked by uid 48); 21 Nov 2014 12:37:58 -0000 From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/64012] GCC-4.9.2 option -fcaller-saves in -O2 Date: Fri, 21 Nov 2014 12:38: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.9.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: <bug-64012-4-tQGneamNri@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-64012-4@http.gcc.gnu.org/bugzilla/> References: <bug-64012-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-11/txt/msg02406.txt.bz2 Content-length: 448 https://gcc.gnu.org/bugzilla/show_bug.cgi?idd012 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Please report to linaro.
next prev parent reply other threads:[~2014-11-21 12:25 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-63230-4@http.gcc.gnu.org/bugzilla/> 2014-09-11 23:30 ` dominiq at lps dot ens.fr 2014-11-21 12:24 ` matthew.hambley at metoffice dot gov.uk 2014-11-21 12:25 ` matthew.hambley at metoffice dot gov.uk [this message] 2014-11-30 18:12 ` dominiq at lps dot ens.fr 2015-03-19 13:39 ` vehre at gcc dot gnu.org 2015-03-19 15:39 ` vehre at gcc dot gnu.org 2015-03-24 10:41 ` vehre at gcc dot gnu.org 2015-03-25 9:58 ` vehre 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-63230-4-Ws3sQNlvQC@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).