public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot 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: Sun, 11 Mar 2007 19:43:00 -0000 [thread overview] Message-ID: <20070311194323.10089.qmail@sourceware.org> (raw) In-Reply-To: <bug-31067-10259@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from tkoenig at gcc dot gnu dot org 2007-03-11 19:43 ------- I have looked at this some more. Channging gfc_conv_intrinsic_function so that we call gfc_conv_intrinsic_minmaxloc is easy enough: @@ -3481,7 +3481,9 @@ gfc_conv_intrinsic_function (gfc_se * se name = &expr->value.function.name[2]; - if (expr->rank > 0 && !expr->inline_noncopying_intrinsic) + if (expr->rank > 0 && !expr->inline_noncopying_intrinsic + && ! (expr->rank == 1 && (isym->generic_id == GFC_ISYM_MINLOC + || isym->generic_id == GFC_ISYM_MAXLOC))) { lib = gfc_is_intrinsic_libcall (expr); if (lib != 0) If we do that, we hit the "if (se->ss)" contition on top of that function, and we would have to handle scalarization of that one-trip loop. I have currently no idea how to go about that. Simply removing the condition doesn't work :-) As a workaround, one could always use "minloc(...,dim=1)", then we get the inline version. Unassigning myself. -- tkoenig at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|tkoenig at gcc dot gnu dot |unassigned at gcc dot gnu |org |dot org Status|ASSIGNED |NEW http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31067
next prev parent reply other threads:[~2007-03-11 19:43 UTC|newest] Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top 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 [this message] 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 [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 2011-07-29 7:13 ` 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=20070311194323.10089.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: 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).