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 tree-optimization/21278] New: Move maximum out of a loop
Date: Fri, 29 Apr 2005 08:17:00 -0000	[thread overview]
Message-ID: <20050429081733.21278.tkoenig@gcc.gnu.org> (raw)

This could help in reducing the amount of work for bounds
checking.

$ cat mymax.c
#include <stdlib.h>
#include <stdio.h>

int main()
{
  char *p;
  int i,j,n;

  scanf("%d",&n);
  j = 0;
  for (i=0; i<n; i++)
    {
        if (j < i)
            j = i;
    }
    printf("%d\n",j);
    return 0;
}
$ gcc -g -funroll-all-loops -S -O3 -fdump-tree-optimized  mymax.c

still does the do loop:

<L13>:;
  j = 0;
  i = 0;

<L0>:;
  j = MAX_EXPR <j, i>;
  i = i + 1;
  if (i != n.10) goto <L0>; else goto <L4>;

when the loop could be optimized to

    if (n <= 0)
        j = 0;
    else
        j = n-1;

-- 
           Summary: Move maximum out of a loop
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: enhancement
          Priority: P2
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: tkoenig at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2005-04-29  8:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29  8:17 tkoenig at gcc dot gnu dot org [this message]
2005-04-30 17:52 ` [Bug tree-optimization/21278] " pinskia at gcc dot gnu dot 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=20050429081733.21278.tkoenig@gcc.gnu.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: 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).