public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64753] Redundant cmp instruction on x86_64
Date: Wed, 28 Jan 2015 13:31:00 -0000	[thread overview]
Message-ID: <bug-64753-4-mGh7UnwbFV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64753-4@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 3061 bytes --]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64753

--- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Rasmus Villemoes from comment #0)

> At the two places marked # we do a cmp and a conditional jump to .L3, where
> for good measure the same cmp is done again... there's no other path to .L3,
> so it would seem that simply omitting that extra cmp should be ok. 

IIRC postreload redundant compare elimination pass removes these redundant
compares. Unfortunately, the pass is not yet enabled for x86 targets.
>From gcc-bugs-return-475242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 28 13:31:04 2015
Return-Path: <gcc-bugs-return-475242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17995 invoked by alias); 28 Jan 2015 13:31:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17468 invoked by uid 48); 28 Jan 2015 13:30:59 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64757] [5 Regression] ICE in fold_convert_loc, at fold-const.c:2353
Date: Wed, 28 Jan 2015 13:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc assigned_to attachments.created
Message-ID: <bug-64757-4-ELTYTvJFpC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-01/txt/msg03236.txt.bz2
Content-length: 681

https://gcc.gnu.org/bugzilla/show_bug.cgi?idd757

Paul Thomas <pault at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pault at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |pault at gcc dot gnu.org

--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> ---
Created attachment 34607
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id4607&actioníit
Draft patch for the PR

I believe that this regression was caused by the fix for pr60357.

The patch is regtesting right now.

Paul


  parent reply	other threads:[~2015-01-28 13:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 15:06 [Bug target/64753] New: " rv at rasmusvillemoes dot dk
2015-01-28 12:58 ` [Bug target/64753] " rv at rasmusvillemoes dot dk
2015-01-28 13:31 ` ubizjak at gmail dot com [this message]
2024-03-17  7:39 ` pinskia 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=bug-64753-4-mGh7UnwbFV@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).