public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/59494] [4.9 Regression] FAIL: gfortran.dg/vect/fast-math-mgrid-resid.f scan-tree-dump-times optimized "vect_[^\\n]*\\+ " 13 Date: Tue, 14 Jan 2014 09:01:00 -0000 [thread overview] Message-ID: <bug-59494-4-Fbhq26KLOz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59494-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59494 --- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Author: jakub Date: Tue Jan 14 09:00:30 2014 New Revision: 206598 URL: http://gcc.gnu.org/viewcvs?rev=206598&root=gcc&view=rev Log: PR testsuite/59494 * gfortran.dg/vect/fast-math-mgrid-resid.f: Change -fdump-tree-optimized to -fdump-tree-pcom-details in dg-options and cleanup-tree-dump from optimized to pcom. Remove scan-tree-dump-times for vect_\[^\\n\]*\\+, add scan-tree-dump-times for no suitable chains and Executing predictive commoning without unrolling. Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/vect/fast-math-mgrid-resid.f
next prev parent reply other threads:[~2014-01-14 9:01 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-13 13:33 [Bug testsuite/59494] New: " dominiq at lps dot ens.fr 2013-12-13 14:31 ` [Bug testsuite/59494] " dominiq at lps dot ens.fr 2013-12-19 13:34 ` rguenth at gcc dot gnu.org 2013-12-20 13:29 ` jakub at gcc dot gnu.org 2014-01-02 14:28 ` jakub at gcc dot gnu.org 2014-01-13 12:25 ` jakub at gcc dot gnu.org 2014-01-13 12:36 ` dominiq at lps dot ens.fr 2014-01-14 9:01 ` jakub at gcc dot gnu.org [this message] 2014-01-14 9:04 ` jakub 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-59494-4-Fbhq26KLOz@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: linkBe 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).