public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/54932] Invalid loop code generated by Fortran FE for loops with bounds in HIGH(type)
Date: Mon, 18 Mar 2013 10:19:00 -0000 [thread overview]
Message-ID: <bug-54932-4-heTygpA6Eo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54932-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54932
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org,
| |ro at gcc dot gnu.org
--- Comment #15 from Rainer Orth <ro at gcc dot gnu.org> 2013-03-18 10:18:48 UTC ---
Since very recently (between 20130313 and 20130315) gfortran.dg/do_1.f90
execution started to XPASS not only at -O0/-O1, but at every optimisation
level.
I think it would be bad to release 4.8.0 with that testsuite noise, but nothing
has happened on this front for a long time.
How to proceed? Simply remove the xfail, add
-fno-aggressive-loop-optimizations
as Dominique proposed?
Rainer
next prev parent reply other threads:[~2013-03-18 10:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 11:45 [Bug fortran/54932] New: " hubicka at gcc dot gnu.org
2012-10-15 11:49 ` [Bug fortran/54932] " rguenth at gcc dot gnu.org
2012-10-16 19:26 ` burnus at gcc dot gnu.org
2012-10-17 9:23 ` rguenth at gcc dot gnu.org
2012-10-17 10:42 ` burnus at gcc dot gnu.org
2012-10-17 17:03 ` burnus at gcc dot gnu.org
2012-10-17 17:58 ` kargl at gcc dot gnu.org
2012-10-17 18:51 ` burnus at gcc dot gnu.org
2012-10-17 19:21 ` sgk at troutmask dot apl.washington.edu
2012-10-23 13:55 ` hubicka at ucw dot cz
2012-11-18 14:34 ` dominiq at lps dot ens.fr
2012-11-18 16:24 ` tkoenig at gcc dot gnu.org
2013-02-01 13:59 ` dominiq at lps dot ens.fr
2013-02-04 0:17 ` hubicka at ucw dot cz
2013-02-12 18:22 ` dominiq at lps dot ens.fr
2013-03-18 10:19 ` ro at gcc dot gnu.org [this message]
2013-03-18 11:05 ` hubicka at ucw dot cz
2013-03-20 11:39 ` burnus 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-54932-4-heTygpA6Eo@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).