public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kate Hedstrom <kate@ahab.rutgers.edu>
To: burley@gnu.org, egcs@cygnus.com
Cc: robertl@dgii.com
Subject: Re: new test will hang 'make check-g77'
Date: Thu, 12 Mar 1998 10:40:00 -0000	[thread overview]
Message-ID: <199803121842.NAA20390@ahab.rutgers.edu> (raw)

> BTW, I've been assuming I should submit these to Jeff Law for actual
> installation via CVS, but, perhaps, Robert Lipe, you'd be willing to
> do this -- especially since that'd give you a direct opportunity
> to once-over my submissions to help avoid duplication?  Even if
> I had my own CVS access, that might be good, but let me know if
> that seems okay.

I had once said that I would organize the Fortran tests,
although I have to admit that I've been ignoring the egcs lists
for the past several months.  I have some old snippets of code
which once failed under g77, but no commentary about what the
problem was or what fixed it.

> Does anyone know how we can make those tests run with '-fPIC -O'
> so they'll show up as a failure?

I will look into it this weekend unless someone fixes it first.

Kate

             reply	other threads:[~1998-03-12 10:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-12 10:40 Kate Hedstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
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-12 12:44         ` Dave Love
1998-03-11  9:39 ` Craig Burley
1998-03-11  9:39   ` Robert Lipe
1998-03-11 15:53     ` Craig Burley
1998-03-11 12:08       ` Robert Lipe
1998-03-11 17:54     ` Joe Buck

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=199803121842.NAA20390@ahab.rutgers.edu \
    --to=kate@ahab.rutgers.edu \
    --cc=burley@gnu.org \
    --cc=egcs@cygnus.com \
    --cc=robertl@dgii.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).