public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][combine] Check WORD_REGISTER_OPERATIONS normally rather than through preprocessor
Date: Thu, 17 Dec 2015 14:49:00 -0000	[thread overview]
Message-ID: <20151217144935.GA11032@gate.crashing.org> (raw)
In-Reply-To: <567048DD.4050100@foss.arm.com>

Hi Kyrill,

On Tue, Dec 15, 2015 at 05:07:41PM +0000, Kyrill Tkachov wrote:
> As part of the war on conditional compilation here's an #if check on 
> WORD_REGISTER_OPERATIONS that
> seems to have been missed out.
> 
> Bootstrapped and tested on arm, aarch64, x86_64.
> 
> Is it still ok to commit these kinds of conditional compilation conversions?

You could say it is a bugfix, a missed case in the conversion ;-)

> diff --git a/gcc/combine.c b/gcc/combine.c
> index 8601d8983ce345e2129dd047b3520d98c0582842..0658a6dbc6df6862df662bc7842c13ed06b36b04 100644
> --- a/gcc/combine.c
> +++ b/gcc/combine.c
> @@ -11488,10 +11488,10 @@ simplify_comparison (enum rtx_code code, rtx *pop0, rtx *pop1)
>    /* Try a few ways of applying the same transformation to both operands.  */
>    while (1)
>      {
> -#if !WORD_REGISTER_OPERATIONS
>        /* The test below this one won't handle SIGN_EXTENDs on these machines,
>  	 so check specially.  */
> -      if (code != GTU && code != GEU && code != LTU && code != LEU
> +      if (!WORD_REGISTER_OPERATIONS && code != GTU && code != GEU
> +	  && code != LTU && code != LEU

Please keep all the code != together, i.e.

+      if (!WORD_REGISTER_OPERATIONS
+	  && code != GTU && code != GEU && code != LTU && code != LEU

Okay with that change.


Segher

  reply	other threads:[~2015-12-17 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15 17:07 Kyrill Tkachov
2015-12-17 14:49 ` Segher Boessenkool [this message]
2015-12-22 10:39   ` Kyrill Tkachov
2016-04-17 21:25 ` Jeff Law
2016-04-18  9:33   ` Kyrill Tkachov
2016-04-21 11:37     ` Jeff Law

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=20151217144935.GA11032@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kyrylo.tkachov@foss.arm.com \
    /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).