public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Daniel Nilsson <dnilsson@sisoft.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: fortran/8904: Optimization problem in f77 code
Date: Wed, 11 Dec 2002 20:06:00 -0000	[thread overview]
Message-ID: <20021212040601.13201.qmail@sources.redhat.com> (raw)

The following reply was made to PR fortran/8904; it has been noted by GNATS.

From: Daniel Nilsson <dnilsson@sisoft.com>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
   nobody@gcc.gnu.org
Cc:  
Subject: Re: fortran/8904: Optimization problem in f77 code
Date: Wed, 11 Dec 2002 22:57:28 -0500

 Reporter address for this bug should be dnilsson@sisoft.com
 
 Another workaround for this problem is the add the -ffloat-store flag to 
 g77, this makes both -O1 and -O2 optimization produce the correct 
 results. This might point to where to problems lies.
 
 Daniel
 
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8904
 


             reply	other threads:[~2002-12-12  4:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 20:06 Daniel Nilsson [this message]
2002-12-12  7:57 toon

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=20021212040601.13201.qmail@sources.redhat.com \
    --to=dnilsson@sisoft.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).