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/94246] [9/10 Regression] valgrind error for ./gfortran.dg/bessel_5.f90 since r9-1566-g87c789f1c0b2df41
Date: Sat, 21 Mar 2020 22:27:03 +0000	[thread overview]
Message-ID: <bug-94246-4-JEyDnqWbnL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94246-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94246

--- Comment #3 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to kargl from comment #2)
 > So, what happens if you do use the required -fno-range-check
> option?

The code is compiled happily:

$ /home/dcb/gcc/results.20200320.valgrind/bin/gfortran -c -Wall
-fno-range-check gfortran.dg/bessel_5.f90
$

  parent reply	other threads:[~2020-03-21 22:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21  9:14 [Bug fortran/94246] New: valgrind error for ./gfortran.dg/bessel_5.f90 dcb314 at hotmail dot com
2020-03-21 10:34 ` [Bug fortran/94246] [9/10 Regression] valgrind error for ./gfortran.dg/bessel_5.f90 since r9-1566-g87c789f1c0b2df41 marxin at gcc dot gnu.org
2020-03-21 21:10 ` kargl at gcc dot gnu.org
2020-03-21 22:27 ` dcb314 at hotmail dot com [this message]
2020-03-21 23:04 ` sgk at troutmask dot apl.washington.edu
2020-03-23  7:35 ` rguenth at gcc dot gnu.org
2020-03-23 16:21 ` sgk at troutmask dot apl.washington.edu
2020-03-23 19:29 ` anlauf at gcc dot gnu.org
2020-03-23 19:54 ` anlauf at gcc dot gnu.org
2020-03-23 20:20 ` sgk at troutmask dot apl.washington.edu
2020-03-24 17:48 ` pault at gcc dot gnu.org
2020-04-01  9:58 ` burnus at gcc dot gnu.org
2020-04-29 20:52 ` [Bug fortran/94246] [9 " anlauf at gcc dot gnu.org
2020-07-13 19:58 ` dominiq at lps dot ens.fr
2021-01-04  8:15 ` cvs-commit at gcc dot gnu.org
2021-01-04  9:08 ` pault at gcc dot gnu.org

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-94246-4-JEyDnqWbnL@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).