public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/53296] Segfault on non-constant character array constructor containing kind spec Date: Wed, 09 May 2012 17:24:00 -0000 [thread overview] Message-ID: <bug-53296-4-ml54KlDTgh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53296-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53296 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wrong-code CC| |burnus at gcc dot gnu.org Known to fail| |4.6.1, 4.8.0 --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-05-09 17:22:43 UTC --- It also doesn't segfault if one replaces the call by: call rou( [character(len=120) :: "123",uCase("abcde"),uCase("ghij")]) Namely: adding as first item in the constructor list a string literal (which by construction has a known length). According to VALGRIND, the problem is an Invalid free() / delete / delete[] / realloc() in line 10 or, if commented, in line 9. Line 9 is the "call rou" line. With ifort 12.1, the programs seems to work while with cryftn it fails at run time with an illegal instruction. In any case, the program looks valid to me.
next prev parent reply other threads:[~2012-05-09 17:23 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-09 15:53 [Bug fortran/53296] New: " gccbgz.lionm at xoxy dot net 2012-05-09 17:24 ` burnus at gcc dot gnu.org [this message] 2012-05-10 11:29 ` [Bug fortran/53296] " burnus 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-53296-4-ml54KlDTgh@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).