public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: sayle@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, moretti@fe.infn.it,
toon@gcc.gnu.org, toon@moene.indiv.nluug.nl
Subject: Re: fortran/7278: g77 "bug"; the executable misbehave
Date: Sun, 29 Sep 2002 13:36:00 -0000 [thread overview]
Message-ID: <20020929203626.11056.qmail@sources.redhat.com> (raw)
Synopsis: g77 "bug"; the executable misbehave
State-Changed-From-To: feedback->closed
State-Changed-By: sayle
State-Changed-When: Sun Sep 29 13:36:25 2002
State-Changed-Why:
I've confirmed that this PR has been fixed, probably (as Toon
suggests) by Jan's recent fixes. I checked that both t.f
and t1.f did indeed produce different results between -O2
and -O2 -fno-automatic using g77 v3.1. Repeating the tests
with current mainline however produces the same (correct)
output.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7278
next reply other threads:[~2002-09-29 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 13:36 sayle [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-10 1:55 toon
2002-08-22 14:06 Toon Moene
2002-07-11 13:46 toon
2002-07-11 8:36 moretti
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=20020929203626.11056.qmail@sources.redhat.com \
--to=sayle@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=moretti@fe.infn.it \
--cc=toon@gcc.gnu.org \
--cc=toon@moene.indiv.nluug.nl \
/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).