public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/98904] valgrind error in gfc_trans_assignment_1 during bootstrap Date: Wed, 03 Feb 2021 19:10:44 +0000 [thread overview] Message-ID: <bug-98904-4-9uOEC8Kn5H@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98904-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98904 --- Comment #12 from David Binderman <dcb314 at hotmail dot com> --- (In reply to Tobias Burnus from comment #11) > It might be that some code optimizes converts ... > It might be that the either the middle end of GCC does this optimization or > that valgrind does this internally. I don't understand very much of your reply, but if you can replace your two mights with facts, that would be IMHO a step in the right direction. I replaced my existing fprintf code with slightly better code on the obvious conditional: if (flag_coarray == GFC_FCOARRAY_LIB) { fprintf( stderr, "flag_coarray %d\n", flag_coarray); fprintf( stderr, "lhs_caf_attr.codimension %d\n", lhs_caf_attr.codimension); fprintf( stderr, "rhs_caf_attr.codimension %d\n", rhs_caf_attr.codimension); fprintf( stderr, "lhs_caf_attr.allocatable %d\n", lhs_caf_attr.allocatable); fprintf( stderr, "lhs_refs_comp %d\n", lhs_refs_comp); fprintf( stderr, "rhs_caf_attr.allocatable %d\n", rhs_caf_attr.allocatable); fprintf( stderr, "rhs_refs_comp %d\n", rhs_refs_comp); } and, surprisingly, the problem seems to have gone away. Mind you, I did compile with -O2 this time, not -O3 as originally specified, so it looks like I get dodgy results if I build the fortran compiler with -O3. I will avoid this in future. Deeper minds might want to look into this problem some more.
prev parent reply other threads:[~2021-02-03 19:10 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-31 16:44 [Bug fortran/98904] New: " dcb314 at hotmail dot com 2021-01-31 16:52 ` [Bug fortran/98904] " dcb314 at hotmail dot com 2021-01-31 21:38 ` dcb314 at hotmail dot com 2021-02-01 8:54 ` marxin at gcc dot gnu.org 2021-02-01 9:06 ` burnus at gcc dot gnu.org 2021-02-01 9:14 ` dcb314 at hotmail dot com 2021-02-01 9:26 ` marxin at gcc dot gnu.org 2021-02-01 10:25 ` dcb314 at hotmail dot com 2021-02-01 10:26 ` dcb314 at hotmail dot com 2021-02-02 9:03 ` marxin at gcc dot gnu.org 2021-02-03 14:09 ` dcb314 at hotmail dot com 2021-02-03 14:56 ` burnus at gcc dot gnu.org 2021-02-03 19:10 ` dcb314 at hotmail dot com [this message]
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-98904-4-9uOEC8Kn5H@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).