public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc Glisse <marc.glisse@inria.fr>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix PR77826
Date: Thu, 06 Oct 2016 18:44:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.20.1610062035030.1911@laptop-mg.saclay.inria.fr> (raw)
In-Reply-To: <alpine.LSU.2.11.1610051337370.26629@t29.fhfr.qr>

On Wed, 5 Oct 2016, Richard Biener wrote:

>> The following will fix PR77826, the issue that in match.pd matching
>> up two things uses operand_equal_p which is too lax about the type
>> of the toplevel entity (at least for integer constants).
>>
>> Bootstrap / regtest pending on x86_64-unknown-linux-gnu.
>
> The following is what I have applied.
>
> Richard.
>
> 2016-10-05  Richard Biener  <rguenther@suse.de>
>
> 	PR middle-end/77826
> 	* genmatch.c (dt_operand::gen_match_op): Amend operand_equal_p
> 	with types_match for GIMPLE code gen to handle type mismatched
> 	constants properly.

I don't understand the disparity between generic and gimple here. Why let 
(char)1 and (long)1 match in generic but not in gimple? And there are 
probably several transformations in match.pd that could do with an update 
if constants don't match anymore. Or did I misunderstand what the patch 
does?

> 	* match.pd ((X /[ex] A) * A -> X): Properly handle converted
> 	and constant A.

This regressed
int f(int*a,int*b){return 4*(int)(b-a);}

-- 
Marc Glisse

  reply	other threads:[~2016-10-06 18:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04 10:34 Richard Biener
2016-10-05 11:38 ` Richard Biener
2016-10-06 18:44   ` Marc Glisse [this message]
2016-10-07  7:36     ` Richard Biener
2016-10-10  8:47       ` Marc Glisse
2016-10-11  9:09         ` Richard Biener
2016-10-11 20:35           ` Marc Glisse
2016-10-12 11:34             ` Richard Biener
2016-10-12 12:49               ` Marc Glisse
2016-10-12 13:25                 ` Richard Biener
2016-10-13  8:29                   ` Richard Biener
2016-10-15 21:50                     ` Marc Glisse
2016-10-17  7:59                       ` Richard Biener

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=alpine.DEB.2.20.1610062035030.1911@laptop-mg.saclay.inria.fr \
    --to=marc.glisse@inria.fr \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    /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).