public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/39865] ICE in gfc_conv_scalarized_array_ref Date: Thu, 23 Apr 2009 13:57:00 -0000 [thread overview] Message-ID: <20090423135713.4358.qmail@sourceware.org> (raw) In-Reply-To: <bug-39865-87@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from burnus at gcc dot gnu dot org 2009-04-23 13:57 ------- Shorter, but gives not an error message but simply segfaults. (By the way, for all tests I tried, gfortran 4.1 to 4.4 crashes, i.e. it is no regression.) Seemingly, no one had tried before to pass an array to the FMT= argument of a data transfer statement. F2003 has: "9.5.1.1 FMT= specifier in a data transfer statement" [...] "If default-char-expr is an array, it is treated as if all of the elements of the array were specified in array element order and were concatenated." subroutine test (v2) character(len=8) :: v2(:) write (*,v2(1:1)) 1 end subroutine test ==21619== Invalid read of size 4 ==21619== at 0x5317FF: gfc_conv_scalarized_array_ref (trans-array.c:2411) ==21619== by 0x5322F4: gfc_conv_array_ref (trans-array.c:2460) ==21619== by 0x54C971: gfc_conv_variable (trans-expr.c:679) ==21619== by 0x559C4C: set_string (trans-io.c:595) ==21619== by 0x55B8C5: build_dt (trans-io.c:1746) -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu dot | |org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords| |ice-on-valid-code Last reconfirmed|0000-00-00 00:00:00 |2009-04-23 13:57:12 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39865
next prev parent reply other threads:[~2009-04-23 13:57 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-23 12:41 [Bug fortran/39865] New: " jakub at gcc dot gnu dot org 2009-04-23 12:47 ` [Bug fortran/39865] " jakub at gcc dot gnu dot org 2009-04-23 13:07 ` dominiq at lps dot ens dot fr 2009-04-23 13:18 ` jakub at gcc dot gnu dot org 2009-04-23 13:33 ` jakub at gcc dot gnu dot org 2009-04-23 13:50 ` jakub at gcc dot gnu dot org 2009-04-23 13:57 ` burnus at gcc dot gnu dot org [this message] 2009-04-23 14:19 ` jakub at gcc dot gnu dot org 2009-04-23 14:51 ` jakub at gcc dot gnu dot org 2009-04-23 17:34 ` burnus at gcc dot gnu dot org 2009-05-11 17:30 ` jakub at gcc dot gnu dot org 2009-05-12 13:20 ` jakub at gcc dot gnu dot org 2009-05-14 0:01 ` jakub at gcc dot gnu dot org 2009-05-14 6:46 ` jakub 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=20090423135713.4358.qmail@sourceware.org \ --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).