public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/44735] ICE on FORALL with character array pointer
Date: Sun, 17 Mar 2013 15:25:00 -0000 [thread overview]
Message-ID: <bug-44735-4-ZCntf6BqBh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44735-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44735
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2010-07-01 06:21:38 |2013-03-17 15:00
Known to fail| |4.9.0
--- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> 2013-03-17 15:24:44 UTC ---
Still fails:
ig25@linux-fd1f:~/Krempel/Forall> valgrind
/home/ig25/lib/gcc/x86_64-unknown-linux-gnu/4.9.0/f951 bug.f90
==24599== Memcheck, a memory error detector
==24599== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==24599== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==24599== Command: /home/ig25/lib/gcc/x86_64-unknown-linux-gnu/4.9.0/f951
bug.f90
==24599==
bug==24599== Invalid read of size 2
==24599== at 0x786F01: fold_convert_loc(unsigned int, tree_node*,
tree_node*) (tree.h:3797)
==24599== by 0x5FE16F: allocate_temp_for_forall_nest_1(tree_node*,
tree_node*, stmtblock_t*, tree_node**) (trans-stmt.c:3270)
==24599== by 0x5FEA47: gfc_trans_assign_need_temp(gfc_expr*, gfc_expr*,
tree_node*, bool, forall_info*, stmtblock_t*) (trans-stmt.c:3391)
==24599== by 0x602DE0: gfc_trans_forall_1(gfc_code*, forall_info*)
(trans-stmt.c:3868)
==24599== by 0x5A6847: trans_code(gfc_code*, tree_node*) (trans.c:1569)
==24599== by 0x5CD8AE: gfc_generate_function_code(gfc_namespace*)
(trans-decl.c:5397)
==24599== by 0x565800: gfc_parse_file() (parse.c:4468)
==24599== by 0x5A20E5: gfc_be_parse_file() (f95-lang.c:189)
==24599== by 0x94D725: compile_file() (toplev.c:543)
==24599== by 0x94F5A9: toplev_main(int, char**) (toplev.c:1876)
==24599== by 0x5A38454: (below main) (in /lib64/libc-2.15.so)
==24599== Address 0x0 is not stack'd, malloc'd or (recently) free'd
next prev parent reply other threads:[~2013-03-17 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-44735-4@http.gcc.gnu.org/bugzilla/>
2010-12-29 22:18 ` tkoenig at gcc dot gnu.org
2013-03-17 15:25 ` tkoenig at gcc dot gnu.org [this message]
2014-08-29 9:44 ` dominiq at lps dot ens.fr
2014-08-31 14:37 ` tkoenig at gcc dot gnu.org
2015-05-04 14:27 ` fxcoudert at gcc dot gnu.org
2015-05-04 14:31 ` fxcoudert at gcc dot gnu.org
2010-06-30 21:34 [Bug fortran/44735] New: " jkrahn at nc dot rr dot com
2010-07-01 6:21 ` [Bug fortran/44735] " burnus at gcc dot gnu dot org
2010-08-18 18:55 ` pault at gcc dot gnu dot 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-44735-4-ZCntf6BqBh@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).