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 14:09:06 +0000 [thread overview]
Message-ID: <bug-98904-4-G7cruDBuev@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 #10 from David Binderman <dcb314 at hotmail dot com> ---
I added the debug lines
fprintf( stderr, "%d\n", flag_coarray);
fprintf( stderr, "%d\n", lhs_caf_attr.codimension);
fprintf( stderr, "%d\n", rhs_caf_attr.codimension);
fprintf( stderr, "%d\n", lhs_caf_attr.allocatable);
fprintf( stderr, "%d\n", lhs_refs_comp);
fprintf( stderr, "%d\n", rhs_caf_attr.allocatable);
fprintf( stderr, "%d\n", rhs_refs_comp);
around line 11320 of file trans-expr.c, recompiled and re-ran the test.
The output from stderr is
==44799== Conditional jump or move depends on uninitialised value(s)
==44799== at 0x525DE53: __vfprintf_internal (in /usr/lib64/libc-2.32.so)
==44799== by 0x525EA6B: buffered_vfprintf (in /usr/lib64/libc-2.32.so)
==44799== by 0x52491D9: fprintf (in /usr/lib64/libc-2.32.so)
==44799== by 0xFE3B61: gfc_trans_assignment_1(gfc_expr*, gfc_expr*, bool,
bool, bool, bool) (trans-expr.c:11321)
Line 11321 is the second line of debug, so valgrind says
lhs_caf_attr.codimension is uninitialised.
I also got valgrind output for lines 11322, 11323 and 11325.
So it looks to me like the codimension fields and the allocatable
fields are not initialised in this case.
The next stage may be to find out where those fields are supposed
to be initialised and find out why they aren't getting done.
I have no familiarity with fortran or its compiler. Perhaps
someone would be kind enough to point me in the right direction ?
next prev parent reply other threads:[~2021-02-03 14:09 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 [this message]
2021-02-03 14:56 ` burnus at gcc dot gnu.org
2021-02-03 19:10 ` dcb314 at hotmail dot com
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-G7cruDBuev@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).