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] New: valgrind error in gfc_trans_assignment_1 during bootstrap
Date: Sun, 31 Jan 2021 16:44:24 +0000 [thread overview]
Message-ID: <bug-98904-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98904
Bug ID: 98904
Summary: valgrind error in gfc_trans_assignment_1 during
bootstrap
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
I just tried to make a valgrind build of gcc fortran with -O3.
My configure lines are
../trunk.git/configure --prefix=/home/dcb/gcc/$PREFIX \
--disable-bootstrap \
--disable-multilib \
--disable-werror \
--with-pkgversion=$HASH \
--enable-checking=valgrind \
--enable-languages=fortran
sed 's/-O2/-O3/' < Makefile > Makefile.tmp
mv Makefile.tmp Makefile
When compiling source code file omp_lib.f90 in libssp, I get
==147960== Conditional jump or move depends on uninitialised value(s)
==147960== at 0x761595: gfc_trans_assignment_1(gfc_expr*, gfc_expr*, bool,
bool, bool, bool) (trans-expr.c:11340)
==147960== by 0x75FE1C: gfc_trans_assignment(gfc_expr*, gfc_expr*, bool,
bool, bool, bool) (trans-expr.c:11557)
==147960== by 0x71D39A: trans_code(gfc_code*, tree_node*) (trans.c:1922)
==147960== by 0x745B96: gfc_generate_function_code(gfc_namespace*)
(trans-decl.c:6880)
Line 11340 is
&& lhs_caf_attr.codimension && rhs_caf_attr.codimension
As part of
else if (flag_coarray == GFC_FCOARRAY_LIB
&& lhs_caf_attr.codimension && rhs_caf_attr.codimension
&& ((lhs_caf_attr.allocatable && lhs_refs_comp)
|| (rhs_caf_attr.allocatable && rhs_refs_comp)))
{
next reply other threads:[~2021-01-31 16:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 16:44 dcb314 at hotmail dot com [this message]
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
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@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).