public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Bahram.shahrooz at uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one compiled by gfortran being wrong.
Date: Mon, 18 Jan 2021 00:30:30 +0000 [thread overview]
Message-ID: <bug-98701-4-FbjOj8fVcq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98701-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701
--- Comment #16 from Bahram.shahrooz at uc dot edu ---
I spent a good chunk of today to debug. The culprit was two variables that had
not been set equal to 0. I get the same results with g77 on Windows, GFortran
on Mac Big Sur, & AbsoftTools ( I downloaded a trial version to help me debug)
on Mac Big Sur
You guys are so helpful. I truly appreciate your time and.
prev parent reply other threads:[~2021-01-18 0:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 20:47 [Bug fortran/98701] New: " Bahram.shahrooz at uc dot edu
2021-01-15 22:13 ` [Bug fortran/98701] " kargl at gcc dot gnu.org
2021-01-15 23:48 ` jakub at gcc dot gnu.org
2021-01-16 0:30 ` Bahram.shahrooz at uc dot edu
2021-01-16 0:41 ` Bahram.shahrooz at uc dot edu
2021-01-16 0:45 ` sgk at troutmask dot apl.washington.edu
2021-01-16 0:51 ` Bahram.shahrooz at uc dot edu
2021-01-16 1:21 ` sgk at troutmask dot apl.washington.edu
2021-01-16 1:32 ` sgk at troutmask dot apl.washington.edu
2021-01-16 4:48 ` Bahram.shahrooz at uc dot edu
2021-01-16 6:52 ` sgk at troutmask dot apl.washington.edu
2021-01-16 23:20 ` Bahram.shahrooz at uc dot edu
2021-01-17 0:08 ` sgk at troutmask dot apl.washington.edu
2021-01-17 0:09 ` Bahram.shahrooz at uc dot edu
2021-01-17 8:11 ` kargl at gcc dot gnu.org
2021-01-17 9:19 ` tkoenig at gcc dot gnu.org
2021-01-18 0:30 ` Bahram.shahrooz at uc dot edu [this message]
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-98701-4-FbjOj8fVcq@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).