public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rth@gcc.gnu.org
To: David.Billinghurst@riotinto.com, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rth@gcc.gnu.org
Subject: Re: fortran/5651: Optimization (-funroll-loops) error with LAPACK sstebz.f
Date: Mon, 15 Apr 2002 14:45:00 -0000	[thread overview]
Message-ID: <20020415214528.4355.qmail@sources.redhat.com> (raw)

Synopsis: Optimization (-funroll-loops) error with LAPACK sstebz.f

Responsible-Changed-From-To: unassigned->rth
Responsible-Changed-By: rth
Responsible-Changed-When: Mon Apr 15 14:45:27 2002
Responsible-Changed-Why:
    .

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5651


             reply	other threads:[~2002-04-15 21:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15 14:45 rth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-15 20:03 rth
2002-04-14  5:16 Billinghurst, David (CRTS)
2002-04-06  2:25 billingd
2002-03-27 19:16 Craig Rodrigues
2002-03-24  2:29 toon
2002-02-10  6:36 David.Billinghurst

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=20020415214528.4355.qmail@sources.redhat.com \
    --to=rth@gcc.gnu.org \
    --cc=David.Billinghurst@riotinto.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).