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 fortran/31067] MINLOC should sometimes be inlined (gas_dyn is sooooo sloooow) Date: Thu, 28 Jul 2011 20:58:00 -0000 [thread overview] Message-ID: <bug-31067-4-9br7eLbxyn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-31067-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31067 --- Comment #45 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-07-28 20:56:57 UTC --- Author: jakub Date: Thu Jul 28 20:56:50 2011 New Revision: 176897 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=176897 Log: PR fortran/31067 * frontend-passes.c (optimize_minmaxloc): New function. (optimize_expr): Call it. * gfortran.dg/maxloc_2.f90: New test. * gfortran.dg/maxloc_3.f90: New test. * gfortran.dg/minloc_1.f90: New test. * gfortran.dg/minloc_2.f90: New test. * gfortran.dg/minloc_3.f90: New test. * gfortran.dg/minmaxloc_7.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/maxloc_2.f90 trunk/gcc/testsuite/gfortran.dg/maxloc_3.f90 trunk/gcc/testsuite/gfortran.dg/minloc_1.f90 trunk/gcc/testsuite/gfortran.dg/minloc_2.f90 trunk/gcc/testsuite/gfortran.dg/minloc_3.f90 trunk/gcc/testsuite/gfortran.dg/minmaxloc_7.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/frontend-passes.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2011-07-28 20:58 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-31067-4@http.gcc.gnu.org/bugzilla/> 2011-07-25 15:44 ` rguenth at gcc dot gnu.org 2011-07-28 13:52 ` jakub at gcc dot gnu.org 2011-07-28 16:03 ` jakub at gcc dot gnu.org 2011-07-28 20:58 ` jakub at gcc dot gnu.org [this message] 2011-07-29 7:13 ` burnus at gcc dot gnu.org 2007-03-07 10:20 [Bug fortran/31067] New: " fxcoudert at gcc dot gnu dot org 2007-03-07 11:28 ` [Bug fortran/31067] " tkoenig at gcc dot gnu dot org 2007-03-07 12:18 ` fxcoudert at gcc dot gnu dot org 2007-03-07 21:00 ` tkoenig at gcc dot gnu dot org 2007-03-07 21:09 ` fxcoudert at gmail dot com 2007-03-07 21:10 ` tkoenig at gcc dot gnu dot org 2007-03-07 21:29 ` tkoenig at gcc dot gnu dot org 2007-03-08 5:50 ` fxcoudert at gcc dot gnu dot org 2007-03-10 12:34 ` tkoenig at gcc dot gnu dot org 2007-03-11 19:43 ` tkoenig at gcc dot gnu dot org 2007-03-12 19:04 ` pault at gcc dot gnu dot org 2007-03-13 20:12 ` tkoenig at gcc dot gnu dot org 2007-03-26 10:38 ` pault at gcc dot gnu dot org 2007-03-26 11:44 ` pault at gcc dot gnu dot org 2007-04-02 16:44 ` tkoenig at gcc dot gnu dot org 2007-04-02 20:01 ` tkoenig at gcc dot gnu dot org 2007-05-18 20:16 ` jb at gcc dot gnu dot org 2007-05-18 20:20 ` jb at gcc dot gnu dot org 2007-06-15 20:35 ` tkoenig at gcc dot gnu dot org 2007-06-27 14:49 ` jb at gcc dot gnu dot org 2008-01-02 21:03 ` pault at gcc dot gnu dot org 2008-01-02 21:07 ` dominiq at lps dot ens dot fr 2009-07-03 10:00 ` rguenth at gcc dot gnu dot org 2009-07-03 12:19 ` rguenth at gcc dot gnu dot org 2009-07-03 12:41 ` burnus at gcc dot gnu dot org 2009-07-03 12:57 ` rguenth at gcc dot gnu dot org 2009-07-03 13:07 ` burnus at gcc dot gnu dot org 2009-07-05 6:48 ` irar at il dot ibm dot com 2009-07-20 12:04 ` irar at il dot ibm dot com 2009-07-24 7:57 ` jakub at gcc dot gnu dot org 2009-07-24 8:20 ` burnus at gcc dot gnu dot org 2009-07-24 8:30 ` jakub at gcc dot gnu dot org 2009-07-26 7:48 ` irar at il dot ibm dot com 2009-07-26 9:50 ` burnus at gcc dot gnu dot org 2009-07-27 8:36 ` irar at il dot ibm dot com 2009-07-27 9:18 ` burnus at gcc dot gnu dot org 2009-07-27 11:03 ` jakub at gcc dot gnu dot org 2009-07-27 11:10 ` jakub at gcc dot gnu dot org 2009-07-27 12:44 ` irar at il dot ibm dot com 2009-07-27 13:15 ` burnus at gcc dot gnu dot org 2009-07-27 14:51 ` jakub at gcc dot gnu dot org 2009-07-28 8:12 ` irar at il dot ibm dot com
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-31067-4-9br7eLbxyn@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).