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/50221] Allocatable string length fails with array assignment Date: Sat, 12 May 2012 12:31:00 -0000 [thread overview] Message-ID: <bug-50221-4-Oz9ztyzL5W@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50221-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50221 --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-05-12 12:10:33 UTC --- The following program illustrates some of the problems: a) If the comment lines are removed (i.e. a module is used), there is no valgrind failure and the result is correct. (Note: It requires the patch from PR 53329 with "ns" replaced by "sym->ns".) b) The program (as is) shows no valgrind failure, but the assignment is wrong: "c3", "c3", "c3" instead of "a1", "b2", "c3". c) If one removes the "save,", the result is as with (b) but valgrind shows many errors of the form: Conditional jump or move depends on uninitialised value(s) at 0x4C2C3A9: memcpy@@GLIBC_2.14 (The same failures one gets for the original program of comment 0.) Looking at the dump for (b) - also in comparison with (a) -, I fail to see why one get's ["c1","c1","c1"] - the code looks correct ("S.0" goes from 1 to 3): __builtin_memcpy ((void *) &(*D.1881)[(S.0 + D.1885) + D.1882], (void *) &const[S.0 + -1], (unsigned long) D.1887); In principle, accessing the second argument wrongly should cause that problem. But that one looks okay. I wonder more about the left as (*D.1881)[...] assumes that the compiler knows the size of one element - I am not sure that that works as ".str" is not yet the right value before the line: character(kind=1)[0:][1:.str] * restrict D.1881; !module m character(len=:), save, allocatable :: str(:) character(len=2), parameter :: const(3) = ["a1", "b2", "c3"] !end !use m call test() if(allocated(str)) deallocate(str) contains subroutine test() call doit() print *, 'strlen=',len(str),' / array size =',size(str) print '(3a)', '>',str(1),'<' print '(3a)', '>',str(2),'<' print '(3a)', '>',str(3),'<' end subroutine test subroutine doit() str = const end subroutine doit end
next prev parent reply other threads:[~2012-05-12 12:11 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-28 21:40 [Bug fortran/50221] New: " clivegpage at gmail dot com 2011-08-29 7:57 ` [Bug fortran/50221] " burnus at gcc dot gnu.org 2012-05-12 12:31 ` burnus at gcc dot gnu.org [this message] 2013-06-16 14:31 ` dominiq at lps dot ens.fr
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-50221-4-Oz9ztyzL5W@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).