public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <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: Mon, 01 Feb 2021 09:26:40 +0000	[thread overview]
Message-ID: <bug-98904-4-3TNGuNSxMt@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 #6 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to David Binderman from comment #5)
> Another test case. I compiled source code file dcabs1.f, from the lapack
> package.
> 
> I got
> 
> $ /home/dcb/gcc/results.20210131.valgrind/bin/gfortran dcabs1.f
> ==76833== Conditional jump or move depends on uninitialised value(s)
> ==76833==    at 0x761595: gfc_trans_assignment_1(gfc_expr*, gfc_expr*, bool,
> bool, bool, bool) (trans-expr.c:11340)
> ==76833==    by 0x75FE1C: gfc_trans_assignment(gfc_expr*, gfc_expr*, bool,
> bool, bool, bool) (trans-expr.c:11557)
> ==76833==    by 0x71D39A: trans_code(gfc_code*, tree_node*) (trans.c:1922)
> ==76833==    by 0x745B96: gfc_generate_function_code(gfc_namespace*)
> (trans-decl.c:6880)
> 
> Version of lapack is lapack-3.9.0. Note no optimiser.

Can you please point to the source file.

And can you please use the following valgrind option:
--expensive-definedness-checks=yes ?

  parent reply	other threads:[~2021-02-01  9:26 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 [this message]
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-3TNGuNSxMt@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).