public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/66588] combine should try transforming if_then_else of zero_extends into zero_extend of if_then_else
Date: Fri, 19 Jun 2015 08:26:00 -0000	[thread overview]
Message-ID: <bug-66588-4-9HJRme8ymc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66588-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from ktkachov at gcc dot gnu.org ---
(In reply to Uroš Bizjak from comment #2)
> (In reply to Uroš Bizjak from comment #1)
> > BTW: x86_64 is missing any form of zero-extended cmove.
> 
> ... please see [1] how x86_64 implements it (*movsicc_noc_zext).
> 
> [1] https://gcc.gnu.org/ml/gcc-patches/2015-06/msg01306.html

Thanks. As I mentioned in the original post this approach does work.
I was just hoping to argue that combine should automatically try both the
(zero_extend (if_then_else a b c))
and
(if_then_else a (zero_extend b) (zero_extend c))

In fact, wouldn't transforming:
(if_then_else a (zero_extend b) (zero_extend c))
into
(zero_extend (if_then_else a b c))
be considered a simplification
suitable for simplify-rtx.c ?
>From gcc-bugs-return-489379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 19 08:36:27 2015
Return-Path: <gcc-bugs-return-489379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94352 invoked by alias); 19 Jun 2015 08:36:27 -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 94300 invoked by uid 48); 19 Jun 2015 08:36:23 -0000
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66578] [F2008] Invalid free on allocate(...,source=a(:)) in block
Date: Fri, 19 Jun 2015 08:36: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: 6.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mikael at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: vehre at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66578-4-KlSPjALu8q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66578-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66578-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-06/txt/msg01711.txt.bz2
Content-length: 487

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

--- Comment #10 from Mikael Morin <mikael at gcc dot gnu.org> ---
(In reply to Thomas Koenig from comment #9)
> Unfortunately, this does not appear to fix the bug (at least not completely).
> I still get an invalid free.

Indeed, unfortunately this:

(In reply to Mikael Morin from comment #7)
> Don't care about the scalarizer; generate a correct descriptor to begin
> with, and the scalarizer will follow (hopefully).

is not true.


  parent reply	other threads:[~2015-06-19  8:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 13:39 [Bug middle-end/66588] New: " ktkachov at gcc dot gnu.org
2015-06-18 14:17 ` [Bug middle-end/66588] " ubizjak at gmail dot com
2015-06-18 19:33 ` ubizjak at gmail dot com
2015-06-19  8:26 ` ktkachov at gcc dot gnu.org [this message]
2015-07-05 16:28 ` segher at gcc dot gnu.org
2015-07-06 10:33 ` ktkachov at gcc dot gnu.org
2023-04-19 15:45 ` cvs-commit 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-66588-4-9HJRme8ymc@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).