public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: anamax@earthlink.net
To: gcc-gnats@gcc.gnu.org
Subject: optimization/7270: Redundant compares not eliminated on x86.
Date: Wed, 10 Jul 2002 22:46:00 -0000	[thread overview]
Message-ID: <20020711053656.11031.qmail@sources.redhat.com> (raw)


>Number:         7270
>Category:       optimization
>Synopsis:       Redundant compares not eliminated on x86.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          pessimizes-code
>Submitter-Id:   net
>Arrival-Date:   Wed Jul 10 22:46:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Andy Freeman
>Release:        gcc 3.1
>Organization:
>Environment:
Redhat 7.3
>Description:
A <= compare&branch followed by a == test on the same arguments uses a redundant compare for the == on x86.

Using built-in specs.
Configured with: ../gcc-3.1/configure 
Thread model: single
gcc version 3.1
>How-To-Repeat:
Look at the -O3 -S output for x86.  Notice the two cmpls on either side of the "ja .L4".  I believe that the second cmpl is unnecessary as the flags from the first should survive the "ja .L4".
>Fix:
Better value propagation.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="ii.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="ii.cc"

dW5zaWduZWQgZm9vKHVuc2lnbmVkIGFbXSkgew0KICBmb3IoIHVuc2lnbmVkIGkgPSAwOyBpIDwg
MTA7ICsraSApIHsNCiAgICBpZiggaSA8PSBhW2ldICkgew0KICAgICAgaWYoIGkgPT0gYVtpXSAp
IHsNCglyZXR1cm4gOTsNCiAgICAgIH0gZWxzZSB7DQoJcmV0dXJuIDE1Ow0KICAgICAgfQ0KICAg
IH0NCiAgfQ0KfQ0K


             reply	other threads:[~2002-07-11  5:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10 22:46 anamax [this message]
2003-05-13 18:56 Dara Hazeghi
2003-05-14 10:28 giovannibajo

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=20020711053656.11031.qmail@sources.redhat.com \
    --to=anamax@earthlink.net \
    --cc=gcc-gnats@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).