public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: tbsaunde+gcc@tbsaunde.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 4/7] don't compare ARG_FRAME_POINTER_REGNUM and FRAME_POINTER_REGNUM with the preprocessor
Date: Thu, 21 May 2015 12:28:00 -0000	[thread overview]
Message-ID: <555DCDC7.6030108@redhat.com> (raw)
In-Reply-To: <1432174178-29086-5-git-send-email-tbsaunde+gcc@tbsaunde.org>

On 05/20/2015 08:09 PM, tbsaunde+gcc@tbsaunde.org wrote:
> From: Trevor Saunders <tbsaunde+gcc@tbsaunde.org>
>
> gcc/ChangeLog:
>
> 2015-05-20  Trevor Saunders  <tbsaunde+gcc@tbsaunde.org>
>
> 	* *.c: Remove comparison of ARG_FRAME_POINTER_REGNUM and
> 	FRAME_POINTER_REGNUM with the preprocessor.
This only hits a handful of files.  If you could go ahead and list them 
in the ChangeLog that'd probably be better than *.c :-)

> @@ -3781,16 +3778,14 @@ df_exit_block_uses_collect (struct df_collection_rec *collection_rec, bitmap exi
>       df_ref_record (DF_REF_ARTIFICIAL, collection_rec, regno_reg_rtx[i], NULL,
>   		   EXIT_BLOCK_PTR_FOR_FN (cfun), NULL, DF_REF_REG_USE, 0);
>
> -#if FRAME_POINTER_REGNUM != ARG_POINTER_REGNUM
>     /* It is deliberate that this is not put in the exit block uses but
>        I do not know why.  */
> -  if (reload_completed
> +  if (FRAME_POINTER_REGNUM != ARG_POINTER_REGNUM && reload_completed
Minor nit, go ahead and put the && reload_completed on the next line. 
While it fits in 80 columns, ISTM like it more naturally (in GNU style) 
belongs on its own line.  Interestingly enough this is the only instance 
where you formatted this way -- all the others have the FP/AP comparison 
on on its own line.

OK for the trunk.

jeff

      reply	other threads:[~2015-05-21 12:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21  2:11 [PATCH 0/7] Some ifdef removal tbsaunde+gcc
2015-05-21  2:11 ` [PATCH 3/7] move default for STACK_PUSH_CODE to defaults.h tbsaunde+gcc
2015-05-21 12:32   ` Jeff Law
2015-05-21  2:11 ` [PATCH 1/7] always define STACK_GROWS_DOWNWARD tbsaunde+gcc
2015-05-21 12:38   ` Jeff Law
2015-05-21 16:59   ` Joseph Myers
2015-05-21  2:11 ` [PATCH 6/7] remove #if HAVE_conditional_move tbsaunde+gcc
2015-05-21 12:31   ` Jeff Law
2015-05-21  2:11 ` [PATCH 5/7] always define HAVE_conditional_move tbsaunde+gcc
2015-05-21 12:29   ` Jeff Law
2015-05-21  2:11 ` [PATCH 2/7] remove most ifdef STACK_GROWS_DOWNWARD tbsaunde+gcc
2015-05-21 12:33   ` Jeff Law
2015-05-21  5:13 ` [PATCH 7/7] always define HAVE_peephole tbsaunde+gcc
2015-05-21  6:17   ` Jeff Law
2015-05-21  5:35 ` [PATCH 4/7] don't compare ARG_FRAME_POINTER_REGNUM and FRAME_POINTER_REGNUM with the preprocessor tbsaunde+gcc
2015-05-21 12:28   ` Jeff Law [this message]

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=555DCDC7.6030108@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tbsaunde+gcc@tbsaunde.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).