public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paulthomas2 at wanadoo dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/18714] Runtime hang in LAPACK routine SLAMC1 - in Quetzal benchmark suite
Date: Fri, 11 Feb 2005 10:00:00 -0000 [thread overview]
Message-ID: <20050210235605.22201.qmail@sourceware.org> (raw)
In-Reply-To: <20041129105735.18714.paul.richard.thomas@cea.fr>
------- Additional Comments From paulthomas2 at wanadoo dot fr 2005-02-10 23:56 -------
Subject: Re: Runtime hang in LAPACK routine SLAMC1 - in Quetzal benchmark suite
PS It seems to me that it is odd that any level of optimisation sends the
programme into an infinite loop. Both ifc and DF6 run find with the maximum
level. I have to agree, though, with the empirical result that this is so
for gfortran!
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18714
next prev parent reply other threads:[~2005-02-10 23:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 10:57 [Bug fortran/18714] New: " paul dot richard dot thomas at cea dot fr
2004-11-30 12:47 ` [Bug fortran/18714] " paul dot richard dot thomas at cea dot fr
2005-01-06 14:43 ` tobi at gcc dot gnu dot org
2005-01-09 4:50 ` giovannibajo at libero dot it
2005-01-28 12:19 ` coudert at clipper dot ens dot fr
2005-01-28 17:02 ` prthomas at drfccad dot cea dot fr
2005-01-28 17:08 ` paulthomas2 at wanadoo dot fr
2005-01-28 17:20 ` coudert at clipper dot ens dot fr
2005-02-11 2:04 ` coudert at clipper dot ens dot fr
2005-02-11 9:56 ` paulthomas2 at wanadoo dot fr
2005-02-11 10:00 ` paulthomas2 at wanadoo dot fr [this message]
2005-02-11 17:10 ` giovannibajo at libero dot it
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=20050210235605.22201.qmail@sourceware.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).