public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Sandoe <idsandoe@googlemail.com>
To: "Shahrooz, Bahram (shahrobm)" <SHAHROBM@UCMAIL.UC.EDU>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>, fortran List <fortran@gcc.gnu.org>
Subject: Re: Erroneous results from gfortran
Date: Fri, 15 Jan 2021 19:24:11 +0000	[thread overview]
Message-ID: <3E3D7437-5E88-466D-864C-24048DAFAC46@googlemail.com> (raw)
In-Reply-To: <D1228DD1-DEED-4C82-852F-F2093CD90C9E@ucmail.uc.edu>

Hello Professor,

Shahrooz, Bahram (shahrobm) via Gcc <gcc@gcc.gnu.org> wrote:

> I’ve used gfortran to compile a program on Mac Big Sur using gcc-10.2 and  
> on Windows 10 using g77.  I’ve used -o0 for both cases.   The results for  
> identical input values are vastly different between the two executables  
> and wrong from gfortran.
>
> I’m not sure if there’s a big in gfortran or something else is causing  
> this issue.

It is impossible to tell from your description.

So far, there is no released version of gfortran that supports the recently  
released macOS 11 (big sur) update, although Intel versions of the platform  
would be expected to be supported from 10.3 onwards.

> I appreciate if you look into this issue.

In order for us to look into the issue we would need to be able to  
reproduce the problem - so some more information is needed - please see:

https://gcc.gnu.org/bugs/

for a description of how to report a bug using

https://gcc.gnu.org/bugzilla/

so that we can try to fix examine and fix it.

thanks.
Iain


           reply	other threads:[~2021-01-15 19:24 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <D1228DD1-DEED-4C82-852F-F2093CD90C9E@ucmail.uc.edu>]

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=3E3D7437-5E88-466D-864C-24048DAFAC46@googlemail.com \
    --to=idsandoe@googlemail.com \
    --cc=SHAHROBM@UCMAIL.UC.EDU \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc@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).