public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "billingd at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/12801] New: [3.4 regression] labug1.f fails
Date: Tue, 28 Oct 2003 01:07:00 -0000 [thread overview]
Message-ID: <20031028010541.12801.billingd@gcc.gnu.org> (raw)
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12801
Summary: [3.4 regression] labug1.f fails
Product: gcc
Version: 3.4
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: billingd at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-cygwin
GCC host triplet: i686-pc-cygwin
GCC target triplet: i686-pc-cygwin
Regression test g77.f-torture/execute/labug1.f execution fails
on i686-pc-cygwin with current CVS head
FAIL: g77.f-torture/execute/labug1.f execution, -O2
FAIL: g77.f-torture/execute/labug1.f execution, -O3 -g
The failure was introduced around Fri Oct 17 2003:
- Passes: Thu Oct 16 08:19:44 GMT 2003
- Fails: Fri Oct 17 14:00:02 GMT 2003
Note that times are approximate as CVS update from local copy.
Independent confirmation on cygwin
http://gcc.gnu.org/ml/gcc-testresults/2003-10/msg01188.html
No evidence on other platforms.
next reply other threads:[~2003-10-28 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 1:07 billingd at gcc dot gnu dot org [this message]
2003-10-28 16:06 ` [Bug optimization/12801] " pinskia at gcc dot gnu dot org
2003-12-03 18:59 ` pinskia at gcc dot gnu dot org
2003-12-19 7:15 ` pinskia at gcc dot gnu dot 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=20031028010541.12801.billingd@gcc.gnu.org \
--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).