public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Gary.White at ColoState dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/109865] different results when routine moved inside the contains statement
Date: Tue, 16 May 2023 15:55:51 +0000 [thread overview]
Message-ID: <bug-109865-4-cKp06dIZ7Z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109865-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865
--- Comment #9 from GARY.WHITE at ColoState dot edu <Gary.White at ColoState dot edu> ---
Another clue. I'm seeing the same bug in gfortran-13, except that I have to
use -O0 for both cases of mc11ad.f90 in or out of the contains statement.
Similarly, if I put the set of va09ad.f90 routines in a module, I have to use
-O0 to get correct answers. -O3 causes a bug with va09ad.f90 in a module as
well.
next prev parent reply other threads:[~2023-05-16 15:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 18:19 [Bug fortran/109865] New: " Gary.White at ColoState dot edu
2023-05-15 18:32 ` [Bug fortran/109865] " anlauf at gcc dot gnu.org
2023-05-15 18:50 ` kargl at gcc dot gnu.org
2023-05-15 19:11 ` Gary.White at ColoState dot edu
2023-05-15 19:24 ` sgk at troutmask dot apl.washington.edu
2023-05-15 20:32 ` Gary.White at ColoState dot edu
2023-05-15 20:41 ` kargl at gcc dot gnu.org
2023-05-15 21:54 ` Gary.White at ColoState dot edu
2023-05-15 22:01 ` Gary.White at ColoState dot edu
2023-05-16 15:55 ` Gary.White at ColoState dot edu [this message]
2023-05-16 21:51 ` sgk at troutmask dot apl.washington.edu
2023-05-16 22:32 ` Gary.White at ColoState dot edu
2023-05-17 0:56 ` Gary.White at ColoState dot edu
2023-05-17 0:56 ` Gary.White at ColoState dot edu
2023-05-17 1:09 ` Gary.White at ColoState dot edu
2023-05-17 3:08 ` jvdelisle at gcc dot gnu.org
2023-05-17 16:49 ` Gary.White at ColoState dot edu
2023-05-17 16:55 ` pinskia 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-109865-4-cKp06dIZ7Z@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).