public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65894] [6 Regression] severe regression in gfortran 6.0.0
Date: Thu, 07 May 2015 19:27:00 -0000	[thread overview]
Message-ID: <bug-65894-4-NWJBXpy1vO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65894-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65894

--- Comment #26 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
With Andre's patch on top of a clean tree at r222878, I get

============================================================================
Testsuite summary for WHIZARD 2.2.6
============================================================================
# TOTAL: 280
# PASS:  107
# SKIP:  28
# XFAIL: 1
# FAIL:  142
# XPASS: 2
# ERROR: 0

After 2 hours I lost patience and killed all the tests requiring more than
~10Gb or more than 5 minutes (~30 of them, on a Corei7 with 16Gb of RAM). I
have no idea if such huge memory usage or long time are expected.

I'll test Mikael's patch at
https://gcc.gnu.org/ml/fortran/2015-05/msg00027.html.


  parent reply	other threads:[~2015-05-07 19:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-26 14:35 [Bug fortran/65894] New: " juergen.reuter at desy dot de
2015-04-26 15:02 ` [Bug fortran/65894] " juergen.reuter at desy dot de
2015-04-27  9:20 ` [Bug fortran/65894] [6 Regression] " rguenth at gcc dot gnu.org
2015-04-27  9:27 ` vehre at gcc dot gnu.org
2015-04-27  9:40 ` juergen.reuter at desy dot de
2015-04-27  9:41 ` juergen.reuter at desy dot de
2015-04-27 16:56 ` vehre at gcc dot gnu.org
2015-04-28  6:33 ` dominiq at lps dot ens.fr
2015-04-28 11:59 ` juergen.reuter at desy dot de
2015-04-28 16:10 ` juergen.reuter at desy dot de
2015-05-05 17:12 ` vehre at gcc dot gnu.org
2015-05-05 17:35 ` juergen.reuter at desy dot de
2015-05-05 18:06 ` vehre at gcc dot gnu.org
2015-05-06  6:54 ` dominiq at lps dot ens.fr
2015-05-07  9:54 ` vehre at gcc dot gnu.org
2015-05-07  9:57 ` juergen.reuter at desy dot de
2015-05-07 10:09 ` vehre at gcc dot gnu.org
2015-05-07 10:14 ` juergen.reuter at desy dot de
2015-05-07 12:10 ` juergen.reuter at desy dot de
2015-05-07 12:20 ` dominiq at lps dot ens.fr
2015-05-07 12:22 ` juergen.reuter at desy dot de
2015-05-07 12:38 ` juergen.reuter at desy dot de
2015-05-07 19:27 ` dominiq at lps dot ens.fr [this message]
2015-05-07 20:46 ` dominiq at lps dot ens.fr
2015-05-08  5:36 ` juergen.reuter at desy dot de
2015-05-08 12:47 ` dominiq at lps dot ens.fr
2015-05-08 18:53 ` dominiq at lps dot ens.fr
2015-05-09 13:36 ` mikael at gcc dot gnu.org
2015-05-10 13:40 ` mikael at gcc dot gnu.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=bug-65894-4-NWJBXpy1vO@http.gcc.gnu.org/bugzilla/ \
    --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).