public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vladimir Makarov <vmakarov@redhat.com>
To: Marek Polacek <polacek@redhat.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix condition in ira-color.c and lra-spills.c (PR c/61271)
Date: Thu, 21 Aug 2014 19:38:00 -0000	[thread overview]
Message-ID: <53F64AB1.4080902@redhat.com> (raw)
In-Reply-To: <20140821180145.GU14320@redhat.com>

On 08/21/2014 02:01 PM, Marek Polacek wrote:
> Both ira-color.c and lra-spills.c contain this code, where
> -Wlogical-not-parentheses would warn:
> !FRAME_GROWS_DOWNWARD == STACK_GROWS_DOWNWARD
> I think the condition is semantically right, so I just tweaked it
> into a more common way with !=, so we don't warn on this anymore.
>
> Bootstrapped/regtested on x86_64-linux, ok for trunk?
>
> 2014-08-21  Marek Polacek  <polacek@redhat.com>
>
> 	PR c/61271
> 	* ira-color.c (coalesced_pseudo_reg_slot_compare): Fix condition.
> 	* lra-spills.c (pseudo_reg_slot_compare): Fix condition.
>
> diff --git gcc/ira-color.c gcc/ira-color.c
> index 36c3c87..14958ac 100644
> --- gcc/ira-color.c
> +++ gcc/ira-color.c
> @@ -3850,7 +3850,7 @@ coalesced_pseudo_reg_slot_compare (const void *v1p, const void *v2p)
>    slot_num2 = -ALLOCNO_HARD_REGNO (a2);
>    if ((diff = slot_num1 - slot_num2) != 0)
>      return (frame_pointer_needed
> -	    || !FRAME_GROWS_DOWNWARD == STACK_GROWS_DOWNWARD ? diff : -diff);
> +	    || (FRAME_GROWS_DOWNWARD != STACK_GROWS_DOWNWARD) ? diff : -diff);
>    total_size1 = MAX (PSEUDO_REGNO_BYTES (regno1),
>  		     regno_max_ref_width[regno1]);
>    total_size2 = MAX (PSEUDO_REGNO_BYTES (regno2),
> diff --git gcc/lra-spills.c gcc/lra-spills.c
> index 50f63fc..0d14685 100644
> --- gcc/lra-spills.c
> +++ gcc/lra-spills.c
> @@ -237,7 +237,7 @@ pseudo_reg_slot_compare (const void *v1p, const void *v2p)
>    slot_num2 = pseudo_slots[regno2].slot_num;
>    if ((diff = slot_num1 - slot_num2) != 0)
>      return (frame_pointer_needed
> -	    || !FRAME_GROWS_DOWNWARD == STACK_GROWS_DOWNWARD ? diff : -diff);
> +	    || (FRAME_GROWS_DOWNWARD != STACK_GROWS_DOWNWARD) ? diff : -diff);
>    total_size1 = GET_MODE_SIZE (lra_reg_info[regno1].biggest_mode);
>    total_size2 = GET_MODE_SIZE (lra_reg_info[regno2].biggest_mode);
>    if ((diff = total_size2 - total_size1) != 0)
>
>
Sorry, Marek.  I guess it is wrong.  STACK_GROWS_DOWNWARD is only 0 or 1
in these files (it is achieved by redefinition of STACK_GROWS_DOWNWARD
in the files).  FAME_GROWS_DOWNWARD can be 0 or anything non-zero (even
non-constant) as tm.texi contains

@defmac FRAME_GROWS_DOWNWARD
Define this macro to nonzero value if the addresses of local variable slots
are at negative offsets from the frame pointer.
@end defmac

It works now as all machine description files use 1 as non-zero value.

So the documentation should be changed but it is not wise, error prune,
and right now the macro value can be non-constant during compilation
time theoretically.

So you need another way to transform the expressions to get rid of the
warning.

As I remember the code was actually taken from the old RA and not simple
as it looks.

  reply	other threads:[~2014-08-21 19:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-21 18:01 Marek Polacek
2014-08-21 19:38 ` Vladimir Makarov [this message]
2014-08-22 14:51   ` Marek Polacek
2014-08-22 15:33     ` Vladimir Makarov

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=53F64AB1.4080902@redhat.com \
    --to=vmakarov@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=polacek@redhat.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).