From: Robert Lipe <robertl@dgii.com>
To: Craig Burley <burley@gnu.org>
Cc: egcs@cygnus.com
Subject: Re: new test will hang 'make check-g77'
Date: Wed, 11 Mar 1998 09:39:00 -0000 [thread overview]
Message-ID: <19980311113939.56910@dgii.com> (raw)
In-Reply-To: <199803111733.MAA12725@melange.gnu.org>
> >The new testcase
> > g77.f-torture/execute/980310-5.f
> >
> >will hang forever when compiled with -O2 or higher, as a 'make check'
>
> Could you email me this code? I might already have a fix for
I will. If you have cvs access, you can just do a 'cvs update' and
see the file.
> Also, I do plan on submitting pending g77 bugs myself as well,
> so, to avoid duplicating work, could you email me summaries of
> each bug report or test case you're working on adding to the
> data base? (Note that your doing this instead of me amounts
Basically I've been picking through the egcs-bugs archives. There
haven't been a whole lot of fortran cases. If you're not CVS enabled,
I'll send you the 8 or 9 I committed yesterday.
> now, as I've got lots of things on my plate that have been
> suffering lately; adding g77 test cases to the egcs suite is
> quite important, IMO, so whatever you can't get to yourself, I
> do want to make time to do.)
Thanx for the help.
RJL
next prev parent reply other threads:[~1998-03-11 9:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-10 22:15 Robert Lipe
1998-03-11 9:04 ` Dave Love
1998-03-11 12:08 ` Robert Lipe
1998-03-11 15:53 ` Dave Love
1998-03-11 15:53 ` Robert Lipe
1998-03-12 8:07 ` Craig Burley
1998-03-12 11:34 ` Dave Love
1998-03-12 14:50 ` Toon Moene
1998-03-16 20:25 ` Adding g77 test cases to egcs Craig Burley
1998-03-12 12:44 ` new test will hang 'make check-g77' Dave Love
1998-03-11 9:39 ` Craig Burley
1998-03-11 9:39 ` Robert Lipe [this message]
1998-03-11 15:53 ` Craig Burley
1998-03-11 12:08 ` Robert Lipe
1998-03-11 17:54 ` Joe Buck
1998-03-12 10:40 Kate Hedstrom
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=19980311113939.56910@dgii.com \
--to=robertl@dgii.com \
--cc=burley@gnu.org \
--cc=egcs@cygnus.com \
/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).