public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/52537] slow trim function
Date: Fri, 11 May 2012 14:16:00 -0000	[thread overview]
Message-ID: <bug-52537-4-ZuC7OMyUWs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52537-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52537

--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> 2012-05-11 13:56:16 UTC ---
Author: tkoenig
Date: Fri May 11 13:56:06 2012
New Revision: 187406

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=187406
Log:
2012-05-11  Thomas Koenig  <tkoenig@gcc.gnu.org>

    PR fortran/52537
    * frontend-passes.c (optimize_op):  Change
    old-style comparison operators to new-style, simplify
    switch as a result.
    (empty_string):  New function.
    (get_len_trim_call):  New function.
    (optimize_comparison):  If comparing to an empty string,
    use comparison of len_trim to zero.
    Use new-style comparison operators only.
    (optimize_trim):  Use get_len_trim_call.

2012-05-11  Thomas Koenig  <tkoenig@gcc.gnu.org>

    PR fortran/52537
    * gfortran.dg/string_compare_4.f90:  New test.


Added:
    trunk/gcc/testsuite/gfortran.dg/string_compare_4.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/frontend-passes.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2012-05-11 13:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09  8:48 [Bug libfortran/52537] New: " talebi.hossein at gmail dot com
2012-03-09  9:14 ` [Bug libfortran/52537] " burnus at gcc dot gnu.org
2012-03-11  7:51 ` tkoenig at gcc dot gnu.org
2012-03-11 17:19 ` tkoenig at gcc dot gnu.org
2012-03-11 17:28 ` talebi.hossein at gmail dot com
2012-04-12 10:47 ` tkoenig at gcc dot gnu.org
2012-05-11 14:16 ` tkoenig at gcc dot gnu.org [this message]
2012-05-11 19:06 ` tkoenig at gcc dot gnu.org
2012-05-11 19:17 ` tkoenig at gcc dot gnu.org
2012-06-07 14:51 ` tkoenig at gcc dot gnu.org
2012-06-07 16:03 ` talebi.hossein at gmail 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-52537-4-ZuC7OMyUWs@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).