public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <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: Mon, 15 May 2023 18:50:52 +0000 [thread overview] Message-ID: <bug-109865-4-D0ZFXlg6aU@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 kargl at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kargl at gcc dot gnu.org --- Comment #2 from kargl at gcc dot gnu.org --- (In reply to GARY.WHITE@ColoState.edu from comment #0) > Created attachment 55087 [details] > set of subroutines where moving mc11ad inside the contains statement > produces incorrect results > > In the following code, when the subroutine mc11ad is moved inside the > contains statement, incorrect results are produced. Produce wrong results is meaningless as you haven't told what the correct results and wrong results are. A difference in the 7 decimal place for REAL may be entirely possible due to floating point round-off > Options being used to compile the code: > COPTIONS = -cpp -std=f2018 -c -D ieee -D dbleprecision -m64 > -fsignaling-nans -ffpe-summary='invalid','zero','overflow','underflow' -O3 > -funroll-loops -ffast-math What happens if you remove -ffast-math and use -O0 or -O1?
next prev parent reply other threads:[~2023-05-15 18:50 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 [this message] 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 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-D0ZFXlg6aU@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: linkBe 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).